<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Fortum Technology Blog - Medium]]></title>
        <description><![CDATA[Learn more about Fortum’s software engineering culture, technology, architecture and product development - Medium]]></description>
        <link>https://medium.com/fortum-tech?source=rss----32e6561fae3b---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>Fortum Technology Blog - Medium</title>
            <link>https://medium.com/fortum-tech?source=rss----32e6561fae3b---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 00:39:40 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/fortum-tech" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Centralized Inventory of Managed VMs in AWS]]></title>
            <link>https://medium.com/fortum-tech/centralized-inventory-of-managed-vms-in-aws-fcb70daac02f?source=rss----32e6561fae3b---4</link>
            <guid isPermaLink="false">https://medium.com/p/fcb70daac02f</guid>
            <category><![CDATA[infrastructure]]></category>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[aws-systems-manager]]></category>
            <category><![CDATA[automation]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <dc:creator><![CDATA[Sunil Kumar Mohanty]]></dc:creator>
            <pubDate>Tue, 09 Apr 2024 06:07:28 GMT</pubDate>
            <atom:updated>2024-04-09T06:07:28.573Z</atom:updated>
            <content:encoded><![CDATA[<p>In any organization, there is a constant need to manage and operate VMs (virtual machines) centrally. Motivation includes standardization, patch management, better cost management by reservations or savings plans, ensuring compliance, listing instances which have certain applications installed and so on and so forth.</p><p>I would personally prefer to transition away from VMs towards managed services or serverless architecture. That way we abstract the infrastructure management and lower our operational overhead. However, despite our best efforts and good intentions, it is a fact that neither us nor the majority of organizations can completely shift away from having, at least some, virtual machines to manage.</p><p>The predicament arises due to legacy applications, managed services not supporting some use cases (e.g. Timescale DB), ecosystem compatibility (integration with some enterprise tooling), regulatory constraints, licensing considerations and more. So, the natural first step is to ensure we have an accurate, centralized repository of all the VMs configuration.</p><p>The AWS built-in service for configuration management is AWS Config.</p><p>AWS Config’s multi-account and multi-region data aggregation does help with the discoverability of VMs¹. However, its scope is limited to only centralized configuration management. It looks at EC2 instances from the outside and sees its configuration and compliance posture. For example, it helps answer the below questions</p><ul><li>List of all EC2 instances</li><li>List of publicly available EC2 instances</li><li>Instances with specific tags</li><li>Non-compliant instances</li></ul><p>However, Config does not provide any information about an instance from the inside. For that, the <strong>Systems Manager Inventory</strong> comes to the rescue.</p><h3>Systems Manager Inventory — single account view</h3><p>Systems Manager Inventory provides a wealth of metadata and configuration information about managed instances². The information collected by Inventory is as below³</p><ul><li>instance information like InstanceId, OS details, CPU details, etc</li><li>installed applications: such as applications installed through yum, apt</li><li>network configuration: information about IP address, subnet</li><li>aws components: details about aws components installed such as ssm agent</li><li>windows registry keys</li><li>files: information about the filesystem</li><li>custom inventory: Inventory can be used to collect custom metadata like Business name, contact details, etc</li></ul><p>Inventory works with any managed node. A managed node has an SSM agent installed and can communicate with the AWS Systems Manager. So, a managed node can be a VM from other cloud providers, IoT devices, and on-premise servers⁴.</p><p>Inventory for a managed node is collected by running the <em>AWS-GatherSoftwareInventory </em>SSM document (provided by AWS in all accounts) against those instances. The State Manager feature of Systems Manager can then be used to associate the above document against all the instances and run them at a frequency.</p><p>Terraform implementation for this is shown below. It collects inventory for all EC2 instances in an account once a day.</p><pre>resource &quot;aws_ssm_association&quot; &quot;this&quot; {<br>  name = &quot;AWS-GatherSoftwareInventory&quot;<br>  targets {<br>    key    = &quot;InstanceIds&quot;<br>    values = [&quot;*&quot;]<br>  }<br>  schedule_expression = &quot;rate(1 day)&quot;<br>}</pre><p>The solution above gathers inventory information but is limited to an individual account. To meet my ultimate goal of aggregating the data at the organization level i.e. multiple accounts and regions, enter <strong>Resource Data Sync.</strong></p><h3>Resource Data Sync for Inventory — AWS Organization view</h3><p><strong>Resource Data Sync is </strong>a powerful Systems Manager feature that enables the collection of inventory information from multiple AWS Accounts and regions into an S3 bucket. It stores the raw data in JSON format which can then be queried using Athena and integrated with QuickSight for visualization purposes.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QRyG6tRB_SwXPhcO0NKCdw.png" /></figure><p>As shown in the diagram above, resource data sync needs to be set up in all the accounts and in all the region for it to work. The easiest way to implement this is by using Cloudformation Stackset. Below is an example of the template for the stack</p><pre>AWSTemplateFormatVersion: 2010-09-09<br>Description: Cloudformation Template to create resources for Systems Manager Inventory<br>Parameters:<br>  ResourceBucketName:<br>    Type: String<br>    Description: Name of S3 bucket where the inventory data will be stored<br><br>Resources:<br>  ResourceDataSync:<br>    Type: AWS::SSM::ResourceDataSync<br>    Properties:<br>      SyncName: centralized-resource-data-sync<br>      SyncType: SyncToDestination<br>      S3Destination:<br>        BucketName: !Ref ResourceBucketName<br>        BucketRegion: !Ref &#39;AWS::Region&#39;<br>        SyncFormat: JsonSerDe<br><br>  InventoryCollection:<br>    Type: AWS::SSM::Association<br>    Properties:<br>      AssociationName: software-inventory<br>      Name: AWS-GatherSoftwareInventory<br>      ScheduleExpression: &quot;rate(1 day)&quot;<br>      Targets:<br>      - Key: InstanceIds<br>        Values:<br>        - &quot;*&quot;</pre><p>Next, is the integration with Amazon Athena. The data exported by Resource Data Sync is in JSON format and is organized in a structure that enables Glue to automatically create partitions. This is how the root folder structure looks like</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/513/1*p7DdlVbn_s6WFYsmS2wKnA.png" /></figure><p>And below is an example how the detailed structure look like.</p><blockquote>s3://example-inventory-bucket/AWS:Application/accountid=012345678912/region=us-west-1/resourcetype=ManagedInstanceInventory/</blockquote><p>Below code is an example implementation of Glue crawler using Terraform</p><pre>resource &quot;aws_glue_catalog_database&quot; &quot;this&quot; {<br>  name = &quot;ssminventory&quot;<br>}<br><br>resource &quot;aws_glue_crawler&quot; &quot;this&quot; {<br>  database_name = aws_glue_catalog_database.this.name<br>  name          = &quot;inventory&quot;<br>  role          = aws_iam_role.crawler_role.arn<br><br>  s3_target {<br>    exclusions = [<br>      &quot;**/test.json&quot;,<br>    ]<br>    path = &quot;s3://${var.resource_data_sync_bucket_id}&quot;<br>  }<br><br>  configuration = jsonencode(<br>    {<br>      CrawlerOutput = {<br>        Partitions = {<br>          AddOrUpdateBehavior = &quot;InheritFromTable&quot;<br>        }<br>      }<br>      CreatePartitionIndex = true<br>      Version              = 1<br>    }<br>  )<br><br>  recrawl_policy {<br>    recrawl_behavior = &quot;CRAWL_EVERYTHING&quot;<br>  }<br><br>  schema_change_policy {<br>    delete_behavior = &quot;LOG&quot;<br>    update_behavior = &quot;LOG&quot;<br>  }<br><br>  schedule = &quot;rate(1 day)&quot;<br>}<br><br>resource &quot;aws_iam_role&quot; &quot;crawler_role&quot; {<br><br>  name               = &quot;inventory-crawler-role&quot;<br>  path               = &quot;/inventory/&quot;<br>  description        = &quot;Policy used by glue crawler to access resource data sync bucket&quot;<br>  assume_role_policy = data.aws_iam_policy_document.crawler_role_assume_role_policy.json<br>}<br><br>data &quot;aws_iam_policy_document&quot; &quot;crawler_role_assume_role_policy&quot; {<br>  statement {<br>    actions = [&quot;sts:AssumeRole&quot;]<br>    principals {<br>      type        = &quot;Service&quot;<br>      identifiers = [&quot;glue.amazonaws.com&quot;]<br>    }<br>  }<br>}<br><br><br>data &quot;aws_iam_policy_document&quot; &quot;glue_access_resource_data_sync&quot; {<br>  statement {<br>    sid = &quot;s3&quot;<br>    actions = [<br>      &quot;s3:GetObject&quot;,<br>      &quot;s3:PutObject&quot;<br>    ]<br>    resources = [&quot;${var.resource_data_sync_bucket_arn}/*&quot;]<br>    effect    = &quot;Allow&quot;<br>  }<br>}<br><br>resource &quot;aws_iam_role_policy&quot; &quot;glue_access_resource_data_sync&quot; {<br>  name   = &quot;access-resource-data-sync-bucket&quot;<br>  role   = aws_iam_role.crawler_role.id<br>  policy = data.aws_iam_policy_document.glue_access_resource_data_sync.json<br>}<br><br>resource &quot;aws_iam_role_policy_attachment&quot; &quot;glue_service_role&quot; {<br>  role       = aws_iam_role.crawler_role.name<br>  policy_arn = &quot;arn:aws:iam::aws:policy/service-role/AWSGlueServiceRole&quot;<br>}</pre><p>Please note that resource data syncs automatically adds a test.json file in the above folders which should be excluded from the scope of the crawler.</p><p>Unfortunately, the crawler above posed a problem for me while crawling the AWS:Application folder. It creates a partition column called <em>resourcetype</em> because of the <em>resourcetype=ManagedInstanceInventory </em>folder. Additionally, the JSON file also contains the <em>resourcetype</em> field. As a result, catalog table was created with a duplicate <em>resourcetype</em> column leading to an error when querying from Athena. To address the issue, I created the <em>aws_application</em> table manually using terraform and disabled Glue from updating the table schema.</p><p>Finally, I was able to query my complete managed VM inventory 🚀</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/810/1*cxZJh1ciExTbd_LXqLagYw.png" /></figure><p>[1] <a href="https://docs.aws.amazon.com/config/latest/developerguide/aggregate-data.html">https://docs.aws.amazon.com/config/latest/developerguide/aggregate-data.html</a></p><p>[2] <a href="https://docs.aws.amazon.com/systems-manager/latest/userguide/session-manager-getting-started.html">https://docs.aws.amazon.com/systems-manager/latest/userguide/session-manager-getting-started.html</a></p><p>[3] <a href="https://docs.aws.amazon.com/systems-manager/latest/userguide/sysman-inventory-schema.html">https://docs.aws.amazon.com/systems-manager/latest/userguide/sysman-inventory-schema.html</a></p><p>[4] <a href="https://docs.aws.amazon.com/systems-manager/latest/userguide/managed_instances.html">https://docs.aws.amazon.com/systems-manager/latest/userguide/managed_instances.html</a></p><p><strong>About the Author:</strong></p><p><a href="https://www.linkedin.com/in/sunilmohanty/">Sunil Mohanty</a>, Lead Architect (Platform Engineering) at Fortum</p><figure><img alt="Sunil Mohanty" src="https://cdn-images-1.medium.com/max/140/1*xotfAPHn8sJICJtAhTO4hA.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fcb70daac02f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/fortum-tech/centralized-inventory-of-managed-vms-in-aws-fcb70daac02f">Centralized Inventory of Managed VMs in AWS</a> was originally published in <a href="https://medium.com/fortum-tech">Fortum Technology Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How we Built a Finnish Transparency Register Solution on Microsoft Power Platform]]></title>
            <link>https://medium.com/fortum-tech/how-we-built-a-finnish-transparency-register-solution-on-microsoft-power-platform-90a22fa1d5d7?source=rss----32e6561fae3b---4</link>
            <guid isPermaLink="false">https://medium.com/p/90a22fa1d5d7</guid>
            <category><![CDATA[microsoft]]></category>
            <category><![CDATA[compliance]]></category>
            <category><![CDATA[no-code]]></category>
            <category><![CDATA[low-code]]></category>
            <category><![CDATA[power-platform-developers]]></category>
            <dc:creator><![CDATA[Fortum Tech]]></dc:creator>
            <pubDate>Tue, 23 Jan 2024 20:32:28 GMT</pubDate>
            <atom:updated>2024-01-23T20:34:31.696Z</atom:updated>
            <content:encoded><![CDATA[<p>From April 1, 2024 onwards, all Finnish companies are required to collect information on the lobbying activities conducted by their employees. This has been mandated by Finland <a href="https://www.avoimuusrekisteri.fi/">Transparency Register Act</a>, that mandates organizations engaging in lobbying in Finland to report to the Finnish Transparency Register any long-term and systematic lobbying efforts directed at the Finnish Parliament or ministries.</p><p>In preparation for these new requirements — and to enhance the internal coordination and monitoring of our activities — Fortum has developed its own Transparency Register tool. All Fortum employees engaging in activities covered by the Register Act, use this digital tool to report them.</p><p>In this blog post we will share a reference implementation / example of the solution that can be used by other Finnish companies to meet these same requirements. Links to download the sample solution and other related artifacts are provided at the end of this article.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/936/1*17VsQxq-lto2IRL2H4Td1w.png" /></figure><h3>How Did We Approach This Challenge?</h3><p>It was clear that a user-friendly tool, capable of meeting our safety and privacy requirements, that could be developed and made available quickly was needed to ensure a smooth adoption of the new practices and meet the compliance requirements. By leveraging the Microsoft Power Platform and low-code / no-code capabilities, we were able to have an iterative approach while co-developing the solution with the stakeholder group. The solution includes, among other things, a Microsoft Power Apps application, Microsoft Power Automate workflows, and a Microsoft Dataverse database.</p><h3>Step by Step Guide to Build the Solution</h3><p>This blog post walks through the main end user use case, explains the main components contained within the solution and provides instructions on how to deploy and configure the solution for use.</p><h4>Using the solution</h4><blockquote><em>[Note: Screenshots in this section introduce the application in Fortum theme. The solution shared publicly via links in this blog post is devoid of any company-specific branding, including our logos and theme colors.]</em></blockquote><p>We designed our step-by-step instructions to both our internal users and citizen developers who want to build using Microsoft Power Platform. These instructions are the best way to introduce the application and help end users to navigate the key functionalities.</p><h3>Start page</h3><p>Start page consists of four blocks:</p><p>- <strong>Add a lobbying activity</strong><br> Contains short briefing of the Finnish Transparency Register law and a button to open a lobbying activity creation form.</p><p>- <strong>List of all lobbying activities</strong><br> Functionality for the user to navigate to activity listing page. By design all lobbying activities are visible to everyone using the app.</p><p>- <strong>Draft items</strong><br> It is possible to mark a lobbying activity as a draft and fulfill information later. Items are also automatically marked as a draft, if the activity date is in the future or if the activity is created by automation (discussed later).</p><p>- <strong>Useful information</strong><br> This section provides various links for the end user to get more information on the legislation or on the usage of the application. The links Fortum implementation of the app contains are:</p><p>o Fortum intranet article titled “Getting ready for the Transparency Register Act — recording of the first info session available.”</p><p>o Fortum internal general presentation of the Finnish transparency register and its implementation at Fortum</p><p>o Instruction video and a slide deck on how to use the tool</p><p>o Teams channel where the user can ask questions, report bugs and propose new functionality</p><p>o Fortum’s <a href="https://www.fortum.com/about-us/public-affairs/business-ethics-guidelines-lobbying">Business Ethics Guidelines for Lobbying</a></p><p>o The <a href="https://www.avoimuusrekisteri.fi/">Finnish public transparency register</a></p><p>o Transparency register guidelines in <a href="https://julkaisut.valtioneuvosto.fi/handle/10024/164811">Finnish</a>, <a href="https://julkaisut.valtioneuvosto.fi/handle/10024/164812">Swedish</a> and <a href="https://julkaisut.valtioneuvosto.fi/handle/10024/164813">English</a></p><p>o The <a href="https://www.finlex.fi/fi/laki/ajantasa/2023/20230430">Finnish Transparency Register act</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/936/1*DAB-_y1S4Pk3DKg0DmsPVA.png" /></figure><p>For admin team members the start page also contains a toggle button that reveals three additional functionality areas needed to better maintain the data in the solution database.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/472/1*Fl4ng8GF0sVdoJEpGOHllg.png" /></figure><p>- <strong>Manage stakeholders</strong><br> Possibility for the admin team members to add new stakeholders and to edit and deactivate existing ones.</p><p>- <strong>Add new organization</strong><br> Possibility to add new organizational levels to the database. A stakeholder is always related to a specific organizational level. One example of an organizational level is <em>“Finland -&gt; Eduskunta (Finnish Parliament) -&gt; Eduskunnan kanslian virkamies -&gt; Keskuskanslia — Pöytäkirjatoimisto”.</em></p><p>- <strong>Manage topics</strong><br> Each lobbying activity can have primary, secondary and tertiary topics assigned. Topics can be maintained through this functionality. It is also possible for the end user to propose a new topic while creating a new lobbying activity — those proposals are approved and rejected also via this feature.</p><h3>Adding a lobbying activity — basic information</h3><p>Adding a new lobbying activity happens via a form that opens on the activity listing screen. Basic information for the activity needs to be filled in before participants can be added to it.</p><p>Required information for all lobbying activities is:</p><p>- <strong>Event type</strong>: Meeting, Email, Phone call, Message, Political event or Other</p><p>- <strong>Topic description</strong></p><p>- <strong>Event date</strong></p><p>- <strong>Primary topic</strong></p><p>- <strong>Main company contact.</strong></p><p>When all the required information has been filled, the activity can be saved. It is possible to add participants to the activity only after it has been saved.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/936/1*8sud0PKTuV6JMaVhk3FAHQ.png" /></figure><h3>Adding a lobbying activity — participants</h3><p>A lobbying activity can contain multiple participants — both internal and external to the company. External participants are called <em>External stakeholders</em> and internal are called <em>Company employees</em>. On lobbying activity can contain as many internal and external participants as needed.</p><p>Company employees are simply selected from a list of all company Entra ID accounts. External stakeholders are selected from existing stakeholders or, if needed, a new stakeholder can be created.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/936/1*os9rCnCFOjg99-JDEotzIA.png" /></figure><h3>Add a lobbying activity — Creating a new stakeholder</h3><p>As already mentioned, it is also possible to add new stakeholders to the system. All users of the application can attach added stakeholders as participants to their lobbying activities.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/936/1*e2Ryk1S8xsHgeORB_SWLBA.png" /></figure><h3>View and manage lobbying activities</h3><p>The user can view a list of all lobbying activities entered in the system. He can also utilize a robust search to look for activities based on specific search criteria. Security roles of the system are very permissive:</p><p>- All users can create new lobbying activities</p><p>- All users can view all lobbying activities (including drafts)</p><p>- All users can modify and remove existing lobbying activities (although a confirmation dialog is displayed upon deletion)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/936/1*570IbwWM2Alwo6f-6lHgJw.png" /></figure><h3>Creating lobbying activities via automation</h3><p>As we wanted to make the creation of new lobbying activities as easy as possible to promote adoption of the solution, we implemented automation feature that can be used to create draft versions of activities without having to open the app.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/710/1*1lmQ-vREM4GaDJl-7Y2Z9A.png" /></figure><p>This feature enables users to easily do initial registration of the activity by simply sending an e-mail to specific user account — at Fortum the name of the account is <em>Fortum Transparency Register</em>. The e-mail can be a regular e-mail or it can be a meeting — based on this the type of the activity is automatically set to either <em>Meeting</em> or <em>Email</em>. The mail subject is used as the <em>Topic description</em> and all company employees who are recipients of the e-mail are automatically added as <em>internal participants</em> to the activity. Also those external recipients, who have a corresponding Stakeholder record in the database, are automatically added as <em>external participants</em>.</p><p>The lobbying activity is created as a draft version and the sender of the e-mail is automatically set as the <em>main contact</em> of the activity. Once the activity is created, a Teams message to the sender is posted informing the user of the new activity created and providing a link to open the app.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/936/1*KF0gE60Tp1QCeaifaWkFpA.png" /></figure><h3>Main solution components</h3><p>Main components of the solution are shown in the high-level architecture picture below.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/936/1*-Z7p12RFgJKO2Rb5TB0YtA.png" /></figure><h3>Power Apps canvas app</h3><p>This is the user interface for all the employees involved in lobbying. The app consists of several screens — the main ones introduced in the earlier section.</p><h3>Power Automate flows</h3><p>There are three flows related to the solution, the most important being the one providing automation to create new draft lobbying activity based on a received e-mail. The three flows are:</p><p>- <strong>Contact event draft creation</strong><br> This is the automation flow, that monitors service account’s inbox and creates lobbying activities based on received e-mails. Activities are only created, if the sender e-mail address is found from company Azure AD and if there is no activity already created with the same Conversation Id. Conversation Id is a unique identifier of used to group related email messages into a conversation or thread and it is calculate automatically by Microsoft Outlook based on various fields of the message (main field being the Subject). This identifier is checked in order to prevent duplicate lobbying activity creation in case of multiple messages sent within single email conversation.</p><p>- <strong>Contact event search</strong><br> This flow is responsible of fetching contact events from Dataverse based on user’s search criteria on lobbying activities listing page. Due to the complexity of the database schema and the search capabilities enabled in the UI, the flow assembles a FetchXML query to execute the search against Dataverse API.</p><p>- <strong>Update AAD User info on Participant</strong><br> This little helper flow is triggered whenever <em>Fortum employee</em> field of a <em>Participant</em> record is changed. The flow fetches Display Name of the employee and updates it on the record.</p><h3>Dataverse database</h3><p>All data that is maintained by the system is stored in Dataverse database.</p><p>The solution is published as one unmanaged solution package that you can simply import to your development environment. In the development environment, make necessary changes to the solution, export it as a managed (preferably) solution and import it to your test or production environment. Lobbying activities are stored in a Contact Event table colored in red in the below data model picture.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/936/1*KSSYGNmkvabzdsVGo2MPYQ.png" /></figure><p>The most relevant tables used by the solution are:</p><p>- <strong>Contact Event</strong><br> All lobbying activities are stored as rows in this table.</p><p>- <strong>Topic</strong><br> One lobbying activity can have primary, secondary and tertiary topic — primary topic is required information when creating or modifying an activity via Power Apps UI.</p><p>- <strong>Participant</strong><br> Each lobbying activity contains zero or more participants. Participant row is an activity specific instantiation of either an external (Stakeholder) or internal (Microsoft Entra ID) participant.</p><p>- <strong>Stakeholder</strong><br> Represents external stakeholder in the system, such as ministry officials.</p><p><strong>Organization</strong><br> Organization table is probably the most complex table in the solution. It used to provide a multi-level organization selection when adding a new stakeholder to the system.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/536/1*QA7cvbHnOZZmiE0fmUw_xg.png" /></figure><p><strong>Political party</strong><br> For some organization levels a political party also needs to be defined when creating a new stakeholder. List of available political parties are maintained in this table.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/536/1*KmScEtG30afNlUEOz5iKrA.png" /></figure><ul><li><strong>Microsoft Entra ID</strong><br> This is on or the built-in tables in Dataverse. It is virtual table that provides access to company Azure AD (Entra ID) accounts.</li></ul><p>In addition to the tables introduced above also Dataverse built-in tables User and Team are used to check whether the current user is part of the admin team of not.</p><h3>Deploying the solution</h3><p>The entire solution is packaged into a single Power Platform solution that you can simply import to your target environment as an unmanaged solution.</p><p>It is recommended that you import the solution to a development environment first, where you can make desired modifications to it. After that, you can export the updated solution as a managed solution package and import it to your test and/or production environment.</p><p>Solution name is <strong>StakeholderMeetingRegistry</strong>. When you start importing it, you are presented with the below information.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/532/1*8WHFPePzacPAK49mXtoOtA.png" /></figure><p>Once you proceed, you need to assign connections to each connection reference contained within the solution. While you can use your own credentials for connection in the development environment, it is wise to use a service account in production environment. It is the email inbox of the account defined for Office 365 Outlook connection that is used by automation to create events based on received email messages.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/524/1*2vn5C4PW2gSj27h0i1Uwtw.png" /></figure><p>Next step is to provide some values for Environment Variables.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/528/1*eNyPV-eXyQtA3z7dyh8EHA.png" /></figure><p>- <strong>Is Production</strong><br> Boolean value indicating whether this is the production instance of the solution. This should be set to Yes only for the final production environments.</p><p>- <strong>Service account email</strong><br> Email address of the service account, whose inbox is monitored for automated activity creation.</p><p>- <strong>AppURL</strong><br> URL of the Power Apps app. This URL is provided to end users by automation whenever a user sends an email to the abovementioned inbox and a new lobbying activity is created. <br> <em>NOTE: You need to fill this value later, since you don’t know the app URL yet.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/936/1*fDP1Mn7jWsAGpi8jMdGN5Q.png" /></figure><h3>Configuration and data import</h3><p>Once you have imported the solution, there are some configuration and data related tasks that you may want to do.</p><h3>Reading in organizational levels and political parties</h3><p>Fortum has put great effort to pre-populate a couple of tables with real data. Two CSV files are provided for other companies to be able to take advantage of this work. You can import <em>political parties</em> and <em>organizational structure</em> by browsing to solution’s <strong>Tables</strong> view and selecting <strong>Import data from Excel</strong> as shown below.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/936/1*Js61W0qKPFZ1zx_KmHbsyQ.png" /></figure><h3>Admin team</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/270/1*KuvzvSeUgmCCWh7_jaGzyA.png" /></figure><p>For a user to be able to see the <strong>Toggle admin view</strong> button on the home screen of the app, there must be a Power Platform team called <strong>Transparency Register Admin Users</strong> and the user must be a member of that team.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/608/1*5HA6ikXKbtw-EpUpytjmxw.png" /></figure><h3>Security roles</h3><p>There are two security roles defined in the solution:</p><p>- Stakeholder Meeting Registry User<br> This security role should be assigned to everyone using the app.</p><p>- Stakeholder Meeting Registry Admin<br> This is the security role that should be assigned to <em>Transparency Register Admin Users</em> team.</p><h3>Starting the automation flow</h3><p>The flow to create lobbying activities automatically based on received email messages is turned off by default. At least for production environment this flow should be turned on, if you want your users to be able to take advantage of this feature.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/936/1*fi4fuHYBy_TgHQ-3gSzNuA.png" /></figure><h3>Summary and Key Takeways</h3><p>In this blog post we shared how our Transparency Register tool was designed and developed using Microsoft Power Platform. With this tool, an organization can comply with the new Finnish legislation and to enhance their internal coordination and monitoring of lobbying activities.</p><p>We covered the main features, managing lobbying activities, participants and stakeholders, and leverage automation to create activities based on email messages. We also described the key technology components of the solution: Microsoft Power Apps canvas app, Power Automate flows and Dataverse database. With the step-by-step instructions provided, deploying, and configuring these Microsoft Power Platform components can be done in a few minutes.</p><p>I hope that this blog post has been useful and informative for you. If you are interested in trying out the solution, you can download it from the links below. Please provide any feedback and suggestions on how to improve the solution further in the comments 😊</p><p>- Download link for the solution package<br> <a href="https://bit.ly/fortum-transparency-register-example-solution-package">https://bit.ly/fortum-transparency-register-example-solution-package</a></p><p>- Download link for Organization data<br> <a href="https://bit.ly/fortum-transparency-register-org-data">https://bit.ly/fortum-transparency-register-org-data</a></p><p>- Download link for Political party data<br> <a href="https://bit.ly/fortum-transparency-register-political-parties-data">https://bit.ly/fortum-transparency-register-political-parties-data</a></p><h3>About the Author:</h3><p><a href="https://www.linkedin.com/in/terhoantila/">Terho Antila</a>, Low-Code Center of Excellence Lead at <a href="https://medium.com/fortum-tech">Fortum</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/200/1*WXQKXNinS0YabzM7xHr-Pg.jpeg" /><figcaption>Terho Antila</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=90a22fa1d5d7" width="1" height="1" alt=""><hr><p><a href="https://medium.com/fortum-tech/how-we-built-a-finnish-transparency-register-solution-on-microsoft-power-platform-90a22fa1d5d7">How we Built a Finnish Transparency Register Solution on Microsoft Power Platform</a> was originally published in <a href="https://medium.com/fortum-tech">Fortum Technology Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Step by Step Guide to Create a Slack App for Incoming Webhooks]]></title>
            <link>https://medium.com/fortum-tech/step-by-step-guide-to-create-a-slack-app-for-incoming-webhooks-3d9b799e8ae1?source=rss----32e6561fae3b---4</link>
            <guid isPermaLink="false">https://medium.com/p/3d9b799e8ae1</guid>
            <category><![CDATA[software]]></category>
            <category><![CDATA[slack]]></category>
            <category><![CDATA[developer]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[slackbot]]></category>
            <dc:creator><![CDATA[Fortum Tech]]></dc:creator>
            <pubDate>Thu, 27 Apr 2023 21:38:54 GMT</pubDate>
            <atom:updated>2023-04-27T21:38:54.037Z</atom:updated>
            <content:encoded><![CDATA[<p>Slack is a powerful tool for communication and collaboration within teams. With the ability to integrate with third-party applications using webhooks, it can become an even more efficient platform for software engineers to work on their projects.</p><p>In this article, we will guide you through the process of creating a new Slack application and setting up incoming webhooks, allowing you to streamline your workflow and increase productivity.</p><h3>Steps to create Slack App for Incoming Webhooks</h3><h4>1. Open Slack API Website</h4><p>To get started, navigate to the Slack API website <a href="https://api.slack.com/apps">here</a>. This is the starting point for creating a new Slack application.</p><h4>2. Create a new Slack App</h4><p>Once you are on the Slack API website, click on the “Create New App” button to start creating a new app. Give your app a name that reflects its purpose, such as “Bug Tracker” or “Code Review Tool”.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ckxNQ-bNYRW7oReNlz-17A.jpeg" /><figcaption>Creating a new Slack App and choosing name &amp; workspace</figcaption></figure><h4>3. Choose the App Name and Workspace</h4><p>Choose a name for the app and pick the workspace. Choose the workspace where you want to install the app.</p><blockquote>⚠️ This can be a workspace that you own, or one where you have the appropriate permissions. Nonetheless, <strong>choosing the proper Slack workspace is crucial</strong>. With incoming webhooks, we do not have the ability to move or share the Slack App across different workspaces.</blockquote><p>You can also add a description of your app to give others an idea of what it does.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*irEbWaojuru6cLWI_2cKtA.jpeg" /><figcaption>Selecting the proper Slack workspace</figcaption></figure><h4>4. Customize your App</h4><p>After creating the app, you can customize it by editing its name, description, icon, and background color. This can help you and your team quickly identify the app and differentiate it from others.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*O17jndRzuJccsxXGp0cPqg.jpeg" /><figcaption>Customizing the Slack App display information</figcaption></figure><h4>5. Navigate to “Incoming Webhooks”</h4><p>On the left panel of the Slack API website, navigate to “Incoming Webhooks” and activate the feature by selecting “On”. This will allow you to receive incoming messages from your application.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dOZM3pikyuZjJ_dU1Ij-Ag.jpeg" /><figcaption>Enabling the Incoming Webhooks feature</figcaption></figure><blockquote>⚠️ Something important to consider is how your system integration will interact with Slack. If you are making API calls directly to Slack, then you might not need the incoming webhook, but your Slack bot will need to be added (like a regular user) to the specific Slack channel(s) you want.</blockquote><h4>6. Add a new webhook to your workspace</h4><p>To add a new webhook, click on “Add New Webhook to Workspace” and choose the channel where you want to receive incoming messages. You can choose an existing channel or create a new one.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fNFAuEAT5l6nPfDOpXhZOg.jpeg" /><figcaption>Generating a new Webhook URL</figcaption></figure><p>When choosing a channel, you might be prompt for an approval of the App installation in the workspace.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*f7YkZ64Fo67JTge6XkyZtQ.jpeg" /><figcaption>Additional approval per workspace might be required</figcaption></figure><h4>7. Copy the Incoming Webhook URL</h4><p>After adding the webhook, copy the newly generated Incoming Webhook URL. This is the URL that your application will use to send messages to Slack.</p><blockquote>⚠️ This URL should be treated as a secret. Anyone who has this URL can submit messages to the Slack channel you defined without additional authentication and authorization.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*e4Y6BXdq7hWdWhl3yPkiOg.jpeg" /><figcaption>Copy the generated Webhook URL</figcaption></figure><h4>8. Add additional incoming webhooks (optional)</h4><p>If you want to receive messages from other channels, you can add additional incoming webhooks connected to those channels. This can be useful if you have multiple teams working on different aspects of a project.</p><h4>9. Add collaborators (optional)</h4><p>If you want other team members to be able to manage the app, you can add them as collaborators. This can help to distribute the workload and ensure that everyone has access to the necessary tools and information.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HFT03HN7xOTzQ118FFIyXg.jpeg" /><figcaption>Explore other sections such as Collaborators</figcaption></figure><h3>Summary and Key Takeaways</h3><p>In conclusion, Slack can be a powerful tool for software engineers when used in combination with third-party applications. By following the guide, you can easily create a new Slack application and set up incoming webhooks to streamline your workflow and integrate with third party applications..</p><p>Remember to customize your app and add collaborators as needed to make the most of its potential. With these tools at your disposal, you and your team can work together more efficiently to achieve your goals.</p><h3>About the Author:</h3><p><a href="https://linkedin.com/in/brunoamaroalmeida">Bruno Amaro Almeida</a>, Head of Technology and Architecture at <a href="https://medium.com/fortum-tech">Fortum</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/0*UrOsdeJxBTPQw0r9.jpg" /><figcaption>Bruno Amaro Almeida</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3d9b799e8ae1" width="1" height="1" alt=""><hr><p><a href="https://medium.com/fortum-tech/step-by-step-guide-to-create-a-slack-app-for-incoming-webhooks-3d9b799e8ae1">Step by Step Guide to Create a Slack App for Incoming Webhooks</a> was originally published in <a href="https://medium.com/fortum-tech">Fortum Technology Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[My First 90 days as a Scrum Master in a Startup]]></title>
            <link>https://medium.com/fortum-tech/my-first-90-days-as-a-scrum-master-in-a-startup-36ef5d6ab68d?source=rss----32e6561fae3b---4</link>
            <guid isPermaLink="false">https://medium.com/p/36ef5d6ab68d</guid>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[scrum]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[scrum-master]]></category>
            <dc:creator><![CDATA[Fortum Tech]]></dc:creator>
            <pubDate>Thu, 06 Apr 2023 07:06:44 GMT</pubDate>
            <atom:updated>2023-04-06T07:06:44.559Z</atom:updated>
            <content:encoded><![CDATA[<p>I joined Fortum in November 2019 and was working in the Business Technology portfolio management in order to support all IT development projects. After three years, I wanted to switch to do something more tangible in the Fortum innovation and venturing startup portfolio, which is one of our fastest moving areas.</p><p>Soon I identified a possibility and I joined <a href="https://hiven.energy/">Hiven</a> in the beginning of this year, January 1st as scrum master.</p><p>Hiven, part of <a href="https://valkea.club/portfolio#current-startups">Fortum’s Valkea startup portfolio</a>, is a venture that focuses on defining the enablers to consume energy smarter, cheaper and in a greener way. Hiven customers are energy companies and manufacturers of smart charging and smart heating products.</p><figure><img alt="Hiven Logo" src="https://cdn-images-1.medium.com/max/708/1*0UK5p3cFpoVlhWU0lHrm0g.png" /><figcaption><a href="http://hiven.energy/">Hiven.energy</a></figcaption></figure><p>In order to manage a job rotation to a totally new role it requires significant effort especially with people, including yourself.</p><h3>Understanding the team</h3><p>Hiven has a significant size development team that is located in several sites between Finland, Sweden and Poland. My first priority was to familiarize myself with the team. The development team has been working over a year together and has already implemented solid agile practices. I wanted to know the team members background, roles and responsibilities. In order to do this, I had a short meeting with everyone where I basically asked about the person background, how long she/he has been in the project and how her/his role has been evolving.</p><p>Additionally I asked what are the areas and ways of working that each person saw working well and what are the areas where we could improve. This was nice way to discuss team’s past history and identify successes and earlier challenges.</p><h3>Understanding the ways of working</h3><p>I had the luxury of working the first month in parallel with the previous scrum master. That helped me to monitor how things have been done and how things differ from what has been documented. I was shadowing him for the first one and half weeks after which I started to lead the working sessions and the previous scrum master was supporting me.</p><p>As a positive surprise, the previous sprint retrospective meetings were well-documented in a web application. Documentation was valuable, as I could review past retrospective meetings on my own time to see, what went well, what were the identified areas for improvement and what kind of actions were agreed to accomplish the agreed improvements.</p><p>If past retrospectives would have been done using sticky notes, those could be documented as photos, but in the application, there is no challenge to read different persons handwriting or see which stickers are grouped together and so on.</p><p>Similarly, I studied the project wiki for existing documentation and to understand the product architecture and technical documentation, to better comprehend, what the team is working on and how we have gotten here. Good documentation is essential for any newcomer, no matter what her/his role is.</p><p>As scrum master, I look specifically after the team effectiveness and even I had many ideas how to improve the collaboration, there is a risk to overburden the team with changes, as I identified multiple ways to improve certain agile practices and ways of working. Why this is essential, is that the Hiven development team is delivering high quality results and had no major issues to begin with.</p><p>Good way to support continuous improvement is to discuss one improvement idea at a time and focus few sprints to trial and adjust the new way of working.</p><h3>Understanding the environment</h3><p>Other priority for me as a new team member was to understand our product, markets, customers and product roadmap going forward.</p><p>Hiven has a motivating and sound product vision and mission that I find very appealing. I had an in-depth introduction from our CEO, <strong>Jani Leirimaa</strong>, who explained the plan, market and customers from a business perspective.</p><p>I also met with our Head of Product, <strong>Niraj Vatvani</strong>, to discuss the product status, features and roadmap in details. Niraj explained, how the features are selected to improve the customer value and fulfill the product mission. Niraj also had a preparation meeting with me prior the first sprint planning in order to ensure that I do not have to ask scoping questions in the joint meeting, that others already understood. This helped to keep the sprint planning meeting focused and efficient.</p><p>Based on my findings, I proposed an updated development plan to myself that we have discussed with my line manager. This development plan contains both technical topics as well as other topics that need strengthening in order to be successful in the scrum master role. The main technical area where I will invest my learning time is Amazon Web Services, as I have earlier mainly studied Microsoft Azure based cloud technologies. For the non-technical skills, one of my targets is to build a deeper understanding of the Hiven business and our customers.</p><p>A practical way to learn about our customers and product was to take part of customer problems, their journey and issues. As a newcomer, I could easily identify myself with a Hiven customer, that does not know all the system details. Troubleshooting is also a compelling way to see how the system operates at a detailed level. It is also valuable to understand if the issue is a bug or user error. Both cases need to be addressed in order to make the product better.</p><h3>My Key Learnings</h3><p>Energy business is new area for me. I have learned a lot and many new acronyms have become familiar like OCPP (Open Charger Point Protocol), TSO (Transmission System Operator) and V2H (Vehicle-to-Home) charging. Although there are a lot of acronyms, it is a familiar feeling because earlier in my career I was working in the telco industry, at Nokia, which has also a lot of acronyms! I have kept a list of new terms in my notes and reflect whenever I found myself unsure about the scope of the discussion.</p><p>Similarly, in the first sprint planning and backlog refinement meetings I wanted to be able to contribute more. However, as a newcomer and non-developer it is hard to understand the product, technologies and other details in such a deep level that can immediately support the team. To overcome that gap, I focused in documenting meetings and writing documentation in Confluence. This has helped me to understand the product better and ensure that I use the same terminology as rest of the team.</p><p>One useful way to ensure that I understand the expectations from the stakeholders is to keep asking “how can I help” and based on the answers reflect that my own expectations are set correctly. On the other hand, if the expectations are conflicting, it is always best to discuss the issues as soon as possible to achieve consensus. In my view that is key to succeed in the scrum master role.</p><h3>Conclusion</h3><p>When you are starting in a new position and new team, it is a combination of motivation, learning new things and frustration of things where you find that you could do better.</p><p>You will identify technical and non-technical topics that need additional studies or practicing. Some need short term actions, but some can take longer time and offer way to grow to the next level in your role as scum master.</p><p>These situations where you step outside of your comfort zone are crucial for professional growth and competence development. The typical Finnish way to onboard a new team member is to push the person to the swimming pool and ask them to start swimming. I think I have succeeded in keeping my nose above the water line and most importantly, I feel motivated and well energized when starting my working days.</p><h3>About the Author:</h3><p><a href="https://www.linkedin.com/in/topivirkki">Topi Virkki</a>, Scrum Master at <a href="https://medium.com/fortum-tech">Fortum</a></p><figure><img alt="Topi Virkki photo" src="https://cdn-images-1.medium.com/max/1024/1*LY8JUAuqa68Lijda9W_j9Q.png" /><figcaption>Topi Virkki</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=36ef5d6ab68d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/fortum-tech/my-first-90-days-as-a-scrum-master-in-a-startup-36ef5d6ab68d">My First 90 days as a Scrum Master in a Startup</a> was originally published in <a href="https://medium.com/fortum-tech">Fortum Technology Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Tips & Tricks Upgrading to React 18]]></title>
            <link>https://medium.com/fortum-tech/tips-tricks-upgrading-to-react-18-ece2fc726242?source=rss----32e6561fae3b---4</link>
            <guid isPermaLink="false">https://medium.com/p/ece2fc726242</guid>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[front-end-development]]></category>
            <category><![CDATA[software-architecture]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Fortum Tech]]></dc:creator>
            <pubDate>Tue, 15 Nov 2022 11:59:31 GMT</pubDate>
            <atom:updated>2022-11-15T11:59:20.053Z</atom:updated>
            <content:encoded><![CDATA[<p>This article contains warnings, and errors while upgrading a project to React v18. You may face the same issues and get hints on how to solve those problems.</p><p>In this article we are going to update:</p><ul><li><a href="https://reactjs.org/">react</a></li><li><a href="https://reactjs.org/docs/react-dom.html">react-dom</a></li><li><a href="https://react-redux.js.org/">react-redux</a></li><li><a href="https://redux.js.org/usage/writing-logic-thunks">redux-thunk</a></li><li><a href="https://www.npmjs.com/package/react-router-dom">react-router-dom</a></li><li><a href="https://testing-library.com/docs/react-testing-library/intro/">@testing-library/react</a></li></ul><p>In case you don’t know, React is a free and open-source front-end JavaScript library for building single page application (SPA) based on UI components. This latest React version (18) contains an exciting list of features that are worth exploring!</p><p>Any react application using prior version of react also uses other libraries depending on the application needs. Applications require routing, state management, location services and other features. These libraries need to be upgraded most of the time to work without any errors.</p><h3><strong>Upgrade react</strong></h3><p>The first command to upgrade a project to react v18: yarn add react react-dom</p><p>We use typescript. So, the obvious update is to update typescript definitions for both react and react-dom. Otherwise there is a problem already displayed:</p><p>Could not find a declaration file for module ‘react-dom/client’</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/964/1*SuVSsBdIGCa5YWA5CL3VQw.png" /></figure><p><strong>Are you using Typescript in your project? “react-dom” has a type definition. Let’s install that: </strong>yarn add –D @types/react @types/react-dom</p><p>There is a warning about : ReactDOM.render is no longer supported in React 18</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/944/1*4V1kXli8k6MQSlgEUItLZQ.png" /></figure><h3>Overcoming issues with the new root API</h3><p>There is a step by step guide about how to use the new API: <a href="https://reactjs.org/blog/2022/03/08/react-18-upgrade-guide.html#updates-to-client-rendering-apis">use new root API</a></p><p>I did not use:</p><p>// createRoot(container!) if you use TypeScript</p><p>You may face forbidden non-null assertion issue from Typescript.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/958/1*ufFDXQXE8Ox9c7B8BYUgxQ.png" /></figure><p>Only change I made from the document is this:</p><pre>const container = document.getElementById(&#39;example-root-container&#39;); <br><br>if (container) { <br><br>const root = createRoot(container); <br><br>root.render(&lt;Main /&gt;); <br><br>} </pre><p>Hopefully, you will not face : Type null is not assignable to type Element | DocumentFragment</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/898/1*QbCq6xLHtdNEfzYp14dfUQ.png" /></figure><h3>Adjusting children props</h3><h4><strong>Issue: children props needs to be explicitly listed:</strong></h4><p>For typescript based react project, there is another issue to resolve: <a href="https://reactjs.org/blog/2022/03/08/react-18-upgrade-guide.html#updates-to-typescript-definitions">children props needs to be explicitly listed.</a> Otherwise, there is an error thrown from our project. Property ‘children’ does not exist on type ConfirmationModalProps (an example props used with our confirmation modal).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4gUCOQNUxtpfHs4kKTzaAw.png" /></figure><p>I just added children property in each complaining component as per the react document suggested.children?: React.ReactNode;</p><h3>Fixing react-redux incorrect peer dependency</h3><p>After upgrading the project to React 18, there are requirements to upgrade other related libraries. There are warnings already shown up:</p><p>Warning: “react-redux@7.x.x” has incorrect peer dependency “react@¹⁶.8.3 || ^17”.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/864/1*RxYwzan7dGFTESDDk8s7oQ.png" /></figure><p>We are using react-redux and react-router-dom in the project. Both modules have incorrect peer dependencies. The current version of react-redux and react-router-dom is not compatible with React 18.</p><p>Because of this incompatibility there is a problem with Provider component from “react-redux”;</p><p>“‘Provider’ cannot be used as a JSX component.\n Its instance type ‘Provider&lt;AppAction&gt;’ is not a valid JSX element.\n The types returned by ‘render()’ are incompatible between these types.\n “</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/856/1*Fg_f7nXfKktJkQSKgCMFJA.png" /></figure><p>“react-redux” v8.x.x is React v18 compitable. Let’s update our react-redux following this: npm i react-redux@latest or, yarn add react-redux@latest</p><p>At the time of writing this article, react-redux 8.0.2 was available. Voila! Our app is not complaining about react-redux or Provider component any more.</p><h3>Upgrading react-router-dom to V6</h3><p>warning “react-router-dom &gt; react-router &gt; mini-create-react-context@0.4.1” has incorrect peer dependency “react@⁰.14.0 || ^15.0.0 || ^16.0.0 || ^17.0.0”.</p><p>So, I checked what version of react-router-dom is used in the project using:yarn list react-router-dom</p><p>The above command produces react-router-dom@5.x.0.</p><p>There is already v6 available for react-router-dom. Here comes the update:yarn add react-router-dom</p><p>In our project, <a href="/service/mailto:react-router-dom@6.3.0">react-router-dom@6.3.0</a> was installed.</p><p>And for typescript:yarn add –D @types/react-router-dom</p><h4><strong>No switch, useHistory, Redirect in react-router-dom@v6:</strong></h4><p>From react-router-dom, there are multiple errors:</p><pre>TS2305: Module &#39;&quot;react-router-dom&quot;&#39; has no exported member &#39;Redirect&#39;. <br><br>TS2305: Module &#39;&quot;react-router-dom&quot;&#39; has no exported member &#39;Switch&#39;. <br><br>TS2305: Module &#39;&quot;react-router-dom&quot;&#39; has no exported member &#39;useHistory&#39;. <br><br>Property &#39;exact&#39; does not exist on type &#39;IntrinsicAttributes &amp; (PathRouteProps | LayoutRouteProps | IndexRouteProps)&#39; </pre><p>There is a detailed list of how to <a href="https://reactrouter.com/docs/en/v6/upgrading/v5#upgrade-to-react-router-v6">upgrade to react-router-dom@v6</a></p><ul><li>Switch needs to be converted to Routes</li><li>There is no exact anymore. There is better provision for relative links</li><li>UseHistory becomes useNavigate</li></ul><pre>console.error  <br>  40 Error: Uncaught [Error: useNavigate() may be used only in the context of a &lt;Router&gt; component </pre><ul><li>BrowserRouter should wrap the App / top level component to get rid of the useNavigate() error.</li></ul><h3><strong>Update redux-thunk!</strong></h3><p>Here comes another issue with AppThunk. We are using vanilla redux v8.</p><p>Error states: “Argument of type AppThunk is not assignable to parameter of type AnyAction” — there is a property type missing in type AppThunk but required in type AnyAction.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/878/1*gz5r5e4JuXKwoKp7OLypQQ.png" /></figure><p>The solution is mentioned here: <a href="https://github.com/reduxjs/redux-thunk/issues/333#issuecomment-1109308664">Missing type in AppThunk — issue</a></p><p>I chose: import type {} from ‘redux-thunk/extend-redux’;</p><p>I found out that there is a type error from redux-thunk/extend-redux:</p><p>Cannot find module ‘redux-thunk/extend-redux’ or its corresponding type declarations.</p><p>Redux-thunk/extend-redux is available from version 2.4.1 but our project is using version lower than that.</p><p>So, what’s the obvious action here?<em> </em>yarn add redux-thunk</p><p>All the AppThunk problems are gone.</p><h3><strong>Update @testing-library/react:</strong></h3><blockquote><em>Are you also using @testing-library/react?</em></blockquote><blockquote><em>What is the version of @testing-library/react are you using before upgrading to React v18?</em></blockquote><p>In our project it is <a href="/service/mailto:@testing-library/react@11.x.x">@testing-library/react@11.x.x</a> yarn list @testing-library/react</p><p>According to the testing-library, upgrading to v13.0.0 should resolve the problem of :</p><pre>console.error <br> Warning: ReactDOM.render is no longer supported in React 18. Use createRoot instead. Until you switch to the new API, your app will behave as if it&#39;s running React 17. Learn more: https://reactjs.org/link/switch-to-createroot</pre><p>Let’s upgrade @testing-library:yarn add –D @testing-library/react</p><p>This installed v13.3.0 of @testing-library/react.</p><p>All the console.error about createRoot in testing were gone.</p><p>BUT!</p><p>Here comes another one:</p><pre> console.error <br>  Warning: A suspended resource finished loading inside a test, but the event was not wrapped in act(...).</pre><p>This is the page contains all the tricks to solve the issues regarding act() wrapper — <a href="https://kentcdodds.com/blog/fix-the-not-wrapped-in-act-warning">https://kentcdodds.com/blog/fix-the-not-wrapped-in-act-warning</a></p><p>What’s left next for the upgrade to React v18?</p><h3>About the Author:</h3><p><a href="https://www.linkedin.com/in/sajjadul/">Robin Sajjad</a>, Senior Software Engineer at <a href="https://medium.com/fortum-tech">Fortum</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/240/0*9Ne6QQJidAt9Nqxs" /><figcaption><a href="https://www.linkedin.com/in/sajjadul/">Robin Sajjad</a></figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ece2fc726242" width="1" height="1" alt=""><hr><p><a href="https://medium.com/fortum-tech/tips-tricks-upgrading-to-react-18-ece2fc726242">Tips &amp; Tricks Upgrading to React 18</a> was originally published in <a href="https://medium.com/fortum-tech">Fortum Technology Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Getting to Know the Basics of AWS DynamoDB]]></title>
            <link>https://medium.com/fortum-tech/getting-to-know-the-basics-of-aws-dynamodb-bd7fa667698b?source=rss----32e6561fae3b---4</link>
            <guid isPermaLink="false">https://medium.com/p/bd7fa667698b</guid>
            <category><![CDATA[architecture]]></category>
            <category><![CDATA[database]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Fortum Tech]]></dc:creator>
            <pubDate>Fri, 11 Nov 2022 14:44:38 GMT</pubDate>
            <atom:updated>2022-11-14T07:47:32.009Z</atom:updated>
            <content:encoded><![CDATA[<h3>What is DynamoDB?</h3><p>DynamoDB is a distributed NoSQL database and is provided as a part of AWS service offering. The term NoSQL has broad definition but in general it means non-SQL or non-relational.</p><p>Relational databases, typically associated with SQL, have been known for a long time and inevitably affected how we think about databases. AWS DynamoDB, and NoSQL, is a paradigm shift compared to relational databases. Therefore, it is important to know about the strengths and weaknesses of this type of solution before using it in a production environment.</p><h3>Recap SQL schema design</h3><p>In regular SQL solutions, schema is based on tabular structures and “set theory”. In those, a database has one or multiple tables. In a table each column holds a fixed data type and each row means one record.</p><p>Example schema definition:</p><pre>CREATE TABLE Customers( <br>   userId INTEGER PRIMARY KEY, <br>   name VARCHAR(25) NOT NULL, <br>   surname VARCHAR(25) NOT NULL, <br>   address VARCHAR(255) NOT NULL <br>); </pre><p>This method works well for one-to-one mappings. If we needed to store a list of user’s orders, we would do normalization and create another table such as:</p><pre>CREATE TABLE Orders( <br><br>orderId INTEGER PRIMARY KEY, <br><br>userId VARCHAR(25) NOT NULL, <br><br>FOREIGN KEY(userId) REFERENCES Customers(userId) <br><br>); </pre><p>This setup would allow us to query user and orders data by joining tables using a “JOIN” clause. This type of data and query modelling will work for every SQL database.</p><h3>Comparison with DynamoDB</h3><p>The same use case would look a bit differently with NoSQL. A possible DynamoDB schema to fulfill this challenge could look like the following table:</p><pre>{ <br><br>   &quot;TableName&quot;: &quot;Orders&quot;, <br><br>   &quot;AttributeDefinitions&quot;: [ <br><br>      {  <br><br>         &quot;AttributeName&quot;: &quot;orderId&quot;, <br><br>         &quot;AttributeType&quot;: &quot;S&quot; <br><br>      } <br><br>   ], <br><br>   &quot;KeySchema&quot;: [  <br><br>      {  <br><br>         &quot;AttributeName&quot;: &quot;orderId&quot;, <br><br>         &quot;KeyType&quot;: &quot;HASH&quot; <br><br>      } <br><br>   ] <br><br>} </pre><p>It looks quite different from a relational database schema and, at first glance, might look a bit cryptic. Let’s explore what makes this schema so different.</p><p><strong>Record structure</strong></p><p>As mentioned before, AWS DynamoDB is a NoSQL database, and more specifically a Key-value database.</p><p>Key-value databases store information, known as documents, in the form of hash maps. Similarly, to the dictionaries concept used in programming languages, to access a certain document, we must supply a given key.</p><p>In DynamoDB, a “key” consists of a Partition (hash) key and an optional Sort (range) key. Partition key and Sort key together form a primary key. Similarly to traditional SQL a primary key also uniquely identifies a single record.</p><p>On the other hand, the “value” (document) part isn’t defined in the schema. This is the first notable difference between DynamoDB and SQL.</p><p><strong>Scalar data types</strong></p><p>Both Partition and Sort key can be of type String, Number or Binary. DynamoDB convention states that each type is represented as a shortcut; hence we have S, N and B respectively.</p><p>Notice that data types are simplified compared to relational databases, where we often must deal with a lot of varying types for integers (int, float, double), strings (varchar, text, tinytext) and binary formats (longblob, mediumblob).</p><p><strong>Complex data types</strong></p><p>Additionally, documents can hold JSON-like structures: List (L), Map (M), Set (SS). Documents are not part of the schema but can shape it, to handle complex and advanced use cases.</p><h3>Understanding the Fundamentals for Querying Data</h3><p>In relational databases we can make queries using SQL on each column available in the table. In the case of AWS DynamoDB, SQL approach does not apply and understanding how to query and retrieve data requires some new learnings. The AWS UI Console is a great starting point to gain this knowledge and can be quite enlightening to first time DynamoDB users.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/590/1*9fr0G6Y_o1AGnSRBbmWuVg.png" /><figcaption>Scan/Query Items UI Panel</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/248/1*q_zkNUgLx3j-kv6sxcENOQ.png" /><figcaption>AWS DynamoDB Scan/Query Items UI SortKey Filter</figcaption></figure><p><strong>Scan</strong></p><p>The Scan method returns all the records from the table. There is a natural resemblance to the “full scan” method known from SQL. This association is a fitting design choice that makes users aware that, much like in a relational database, the scan method has a negative performance impact and shouldn’t be used lightly.</p><p><strong>Partition key</strong></p><p>If the table schema has no Sort key defined, the Partition key will become the primary key, resulting in only one record returned by the query.</p><p><strong>Sort key</strong></p><p>Sort key allows us to filter records using range operators. As an example, if we want to store monthly reports of employees, a single record could look like this:</p><p>PK=”employee-123”, SK=”2022–07”</p><p>Using this schema, we can provide Partition key and Sort key to extract a single record. One can include a Sort key filter to return records for a single year or not using the Sort key to retrieve all employee reports.</p><p><strong>Filters</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/1*tvpX_CxSFT7VpL80KTxqyQ.png" /><figcaption>AWS DynamoDB Filters UI Panel</figcaption></figure><p>Filters allow us to narrow down the returned records using fields other than components of the primary key. In SQL, one could use the concept of projections for similar results.</p><p><strong>Index query</strong></p><p>To accelerate data retrieval, one can query a custom index instead of reaching the table directly. While there are some tradeoffs to consider, this method provides an impressive performance boot to retrieve data.</p><h3>Design schema</h3><p><strong>Tabular schema</strong></p><p>In relational databases, table design is very structured. We create a table with columns that match exactly the parameters we want to store.</p><p>Since AWS DynamoDB is a key-value storage it does not have static schema. This can give the wrong impression that schema design is not important (or even possible) in NoSQL databases.</p><blockquote>In an earlier section we learned about querying, which relies on Partition and Sort key. Therefore, the most important questions about table schema are:</blockquote><blockquote>- What value should be used as Partition key?</blockquote><blockquote>- Do I need Sort key capabilities? What values should be used as a Sort key?</blockquote><blockquote>- Do I need indexes?</blockquote><p>Even if we think of a classic tabular schema design, that does not help us to answer these questions. Therefore, it is important to reflect on these questions before taking DynamoDB into real use. Is there a better way to design and plan a DynamoDB schema?</p><p>Instead of thinking of a classic schema design, a better practice is to model our data similarly to files in a directory. We will treat our database as a root directory, partition key as subdirectory and each document as a file.</p><p>This metaphor makes it easy to grasp the concept of querying using Partition key. One needs to know the file path to be able to read the content inside it.</p><p>When you think about content, DynamoDB records can hold JSON-like structures hence we can give our files “*.json” extension. That example would give us simple models such as:</p><p>/Orders/user-3451/record.json</p><p>This approach makes it easier to design and plan a basic schema that would address our user and orders data use case needs.</p><h3>Conclusion</h3><p>In this article, we highlighted the major differences between classic SQL tables and AWS DynamoDB, plus covered basics of data modeling and querying capabilities</p><p>Moreover, we used directory-oriented modelling analogy to make it easier to plan and design a basic AWS DynamoDB schema. In the next article we will expand this concept to involve Sort key, indexes and other advanced functionalities.</p><h3>About the Author:</h3><p><strong>Krzysztof Kurczewski</strong>, Senior Software Engineer at <a href="https://medium.com/fortum-tech">Fortum</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bd7fa667698b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/fortum-tech/getting-to-know-the-basics-of-aws-dynamodb-bd7fa667698b">Getting to Know the Basics of AWS DynamoDB</a> was originally published in <a href="https://medium.com/fortum-tech">Fortum Technology Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How To Create A New GitHub Organization With An OAuth App Setup]]></title>
            <link>https://medium.com/fortum-tech/how-to-create-a-new-github-organization-with-an-oauth-app-setup-4d0e46b17995?source=rss----32e6561fae3b---4</link>
            <guid isPermaLink="false">https://medium.com/p/4d0e46b17995</guid>
            <category><![CDATA[cloud]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[authentication]]></category>
            <category><![CDATA[continuous-integration]]></category>
            <dc:creator><![CDATA[Fortum Tech]]></dc:creator>
            <pubDate>Fri, 13 May 2022 08:18:30 GMT</pubDate>
            <atom:updated>2022-05-05T18:15:45.107Z</atom:updated>
            <content:encoded><![CDATA[<p>Suppose a new developer has joined your team. How to make sure that the developer gets proper access to all the needed GitHub repositories. One way is to add the developer in each GitHub repository as a collaborator.</p><p><strong>But that’s time consuming, repetitive, and does not supply any control mechanisms across the entire organization code repositories.</strong></p><p>It would be great to simply add the developer to a group. A group that already has access to all the required GitHub repositories in that organization and follows the policies and procedures the organization designed.</p><p>Here comes GitHub Organizations. With GitHub Organizations it is possible to define a logical boundary to what are the repositories an organization owns, set up policies, manage employee and third-party application access, gain visibility and insights across the entire organization code base, among many other features. In this article, we will describe how to set up a GitHub Organization and explore its OAuth App functionality. Read on as we cover:</p><ul><li><a href="#2c84\">What are GitHub Organizations?</a></li><li><a href="#fd76">Steps to Create a New GitHub Organization</a></li><li><a href="#5f33">What is an OAuth App?</a></li><li><a href="#e6a4">Creating a new OAuth App in a GitHub Organization</a></li></ul><h3>What are GitHub Organizations?</h3><p>GitHub can be easily adopted by any developer to collaborate across multiple code repositories (e.g., open-source projects). However, only by setting up a GitHub Organization can we aggregate repositories and people that belong to the same organization (e.g., an enterprise or startup). Using GitHub Organizations enables advanced functionalities and allows administrators to set up governance mechanisms that allow people to collaborate and contribute to the same organization.</p><p>In a GitHub Organization a person can have the role of either Owner or Member. An Owner has full control over the organization and can do any action, such as access to organization level APIs (Application Programming Interfaces) and removing the entire organization codebase.</p><p>The Member role does not have access to the organization settings and is limited to accessing a specific repository, or to whatever default organization “base permissions” were set up by the organization Owners.</p><p>A few examples of actions that an organization Owner can do (depending on the plan chosen) are:</p><ul><li>Access to billing and plans</li><li>Set private self-hosted runners for GitHub Actions usage</li><li>Curate an allow list/deny list of GitHub Actions from the Marketplace</li><li>Enable 2-factor authentication</li><li>Store organization level secrets</li><li>Check the audit logs from API (Application Programming Interfaces) calls within the GitHub Organization</li><li>Set up 3rd party apps integration or OAuth app permissions</li></ul><h3>Steps to Create a New GitHub Organization</h3><p>Start by visiting the <a href="https://github.com/">GitHub portal</a> and (if you haven’t already) create a new user account. To create a new GitHub Organization, select the “New organization” choice in the upper right corner dropdown menu (the plus icon near the profile picture).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/1*nUPQJYZDqpN2ZxsW0mq6qA.png" /><figcaption>New GitHub Organization panel</figcaption></figure><p>In the next panel you will be asked to choose from the different GitHub organization plan options. For this guide, the free plan is sufficient, but take note of the features available in each plan.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/932/1*xBuOQywDa3LUIypB7iuS0w.png" /><figcaption>GitHub Organization plans</figcaption></figure><p>Once the organization is created, you can set up your first GitHub team. A team corresponds to a logical group of users. In a GitHub organization the users can belong to multiple teams.</p><p>Select the choice “Teams” and fill in the team’s name (e.g., doet-admins). Keep the other options with their default values and press the “Create team” button.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/1*8fskyuuDeCKfFC9LI5oJdQ.png" /><figcaption>GitHub team creation panel</figcaption></figure><p>In our recently created organization (i.e.: DevOps-Engineers-Team), the team will appear on the list.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/958/1*X2Jt2rPzGuy0LeOgBkKH_A.png" /><figcaption>GitHub teams list</figcaption></figure><p>By assigning users to teams, GitHub Organization administrators can easily manage permissions according to the individual profile and role within the organization.</p><p>When thinking about creating the organization “base permissions”, a good practice is to use only “read” permissions, following a policy of least privileges, meaning that one should only be granted the necessary minimum access level while also promoting transparency and cross-team collaboration within the organization.</p><h3>What is an OAuth App?</h3><p>A GitHub OAuth App enables 3rd party applications to integrate with your GitHub organization by supplying the ability to act as a regular GitHub authorized user. A common misconception is that GitHub Apps and OAuth Apps are the same but in fact there are significant differences between the two. A GitHub user can authorize an OAuth App to have the ability to act as themselves. This enables the OAuth App to impersonate the user and for example, access and read all notifications that were issued to them. At any point in time, the user can choose to revoke the permissions it gave to the OAuth App.</p><p>When an OAuth App is created, Client ID and Client Secret tokens are generated. These tokens follow the <a href="https://oauth.net/">OAuth open standard</a> and can be used by a 3rd party or custom application to authenticate in the GitHub Organization.</p><h3>Creating a new OAuth App in a GitHub Organization</h3><p>To create a new OAuth App, navigate to the <em>Organization settings</em> section found under <em>Developer Settings. Press</em> the <em>New OAuth App </em>button to start the process.</p><p>In this example we are going to create an OAuth App to allow the GitHub Organization users to log into a custom ArgoCD application deployment — a popular continuous delivery solution for Kubernetes — using it’s <a href="https://argoproj.github.io/argo-workflows/argo-server-sso-argocd/">Dex</a> server capability.</p><p>Start by filling in the application name (e.g., argocd-demo), the application homepage URL (e.g., https://argocd.witold-demo.com), a high-level description of the application and last, an Authorization callback URL (e.g., <a href="https://argocd.witold-demo.com/api/dex/callback).">https://argocd.witold-demo.com/api/dex/callback).</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/632/1*IxT9b9SLVJ8VB35WghUXxw.png" /><figcaption>OAuth application configuration setup</figcaption></figure><p>The two most important fields in the configuration are the <em>Homepage URL</em> and <em>Authorization callback URL</em>. The first one is the host domain from where the authentication requests towards GitHub will originate, while the latter is the destination URL to where GitHub should redirect the user once the authentication process is finished.</p><p>Once the OAuth App is creating two important keys are generated: OAuth Client Id and OAuth Client Secret. These keys enable your applications (e.g., ArgoCD) to authenticate and interact with GitHub. Therefore, it is crucial that you store and handle them in an equivalent manner to any user passwords or application secrets.</p><p>A common best practice is to use a secret management service such as AWS Secret Manager, AWS SSM Parameter Store or Hashicorp Vault. In the case of AWS SSM Parameter Store, you could create two parameters named /<em>secrets/core-infra/develop/argocd_oauth_client_id</em> and <em>/secrets/core-infra/develop/argocd_oauth_client_secret</em>, to encrypt and store the two generated keys. This would make it possible for an application to programmatically retrieve and decrypt them on demand via an API by just referencing the parameter name. For example, the get-parameter method in AWS SSM Parameter Store API can be used both via the AWS UI console or programmatically with AWS CLI (Command Line Interface), AWS SDK (Software Development Kit), Terraform data blocks, etc.</p><p>Regardless of what secret management tool you choose the most important thing is that you have a method to store these sensitive keys. Your application doesn’t need to (or shouldn’t) hardcode and remember these values. The keys generated per OAuth App enable anyone who has them to authenticate against your GitHub Organization from anywhere in the world.</p><p>In the enterprise world, you can easily find GitHub Organizations that have several OAuth Apps. Therefore, it is crucial for the organization GitHub Owners, usually people in DevOps and SysOps roles, to show a strict process for their daily operations that restrict who has access to these secrets and how to store them. These practices make the developer experience easy for any GitHub user to rely on secret management services to retrieve the keys rather than sharing plain-texted values.</p><h3>Conclusion</h3><p>As we covered, combining GitHub Organization with OAuth Apps supplies a secure centralized solution for authenticating custom applications. This setup can be easily extended further with added functionalities such as enabling two factor authentication and fine-grained application permissions to retrieve OAuth keys from a secret management service.</p><p>Using OAuth Apps in a GitHub Organization enable platform engineering teams to integrate their multi-vendor tools, such as the ArgoCD application, and set up a fully programmatic GitOps experience with their application codebase, processes and infrastructure (e.g., AWS Elastic Kubernetes Service).</p><h3>About the Author:</h3><p><a href="https://www.linkedin.com/in/witold-slawko/">Witold Sławko</a>, DevOps Engineer at <a href="https://medium.com/fortum-tech">Fortum</a></p><figure><img alt="Witold Slawko" src="https://cdn-images-1.medium.com/max/360/1*IbgsTJb487txX8GQabhshg.jpeg" /><figcaption>Witold Slawko</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4d0e46b17995" width="1" height="1" alt=""><hr><p><a href="https://medium.com/fortum-tech/how-to-create-a-new-github-organization-with-an-oauth-app-setup-4d0e46b17995">How To Create A New GitHub Organization With An OAuth App Setup</a> was originally published in <a href="https://medium.com/fortum-tech">Fortum Technology Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What is TypeScript and why would I use it in place of JavaScript?]]></title>
            <link>https://medium.com/fortum-tech/what-is-typescript-and-why-would-i-use-it-in-place-of-javascript-a2cec0e14764?source=rss----32e6561fae3b---4</link>
            <guid isPermaLink="false">https://medium.com/p/a2cec0e14764</guid>
            <category><![CDATA[front-end-development]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[best-practices]]></category>
            <dc:creator><![CDATA[Fortum Tech]]></dc:creator>
            <pubDate>Fri, 11 Feb 2022 14:16:24 GMT</pubDate>
            <atom:updated>2022-02-11T14:15:52.841Z</atom:updated>
            <content:encoded><![CDATA[<h3>What is TypeScript and why would I use it in place of JavaScript? All You Need to Know to Get Started</h3><p>JavaScript is one of the most popular programming languages and that is for a good reason.</p><p>It is easy to get started with almost no setup. You can just open the browser console and start coding. JavaScript has a strong ecosystem that allows building reliable products fast and securely. From adding an animation to a website to creating large frontend and backend projects from scratch, there are almost no limits to what JavaScript can do in digital development.</p><p><strong>But simplicity comes with its own cost.</strong></p><p>JavaScript makes it easy to fall into a trap of producing unmaintainable code with unpredictable behavior. The main culprit is JavaScript dynamically typed characteristics, which means that types of variables don’t have to be explicitly specified in the code but will be inferred from the value during the run time. On the one hand, it allows developers to quickly write code without having to specify variable types, but on the other hand developers often find themselves searching for a nasty bug that occurs because of the lack of static typings that could have easily prevented that behavior.</p><p>One of the most common errors in JavaScript <em>“</em><em>Cannot read a property of undefined</em>“ happens due to lack of typing’s, where an object is expected to have a specific property, but JavaScript is unable to automatically find it and therefore, we end up with a broken code.</p><p>How can we prevent such types of errors? The answer is simple, add static types to our JavaScript code using TypeScript, a strongly typed programming language that builds on top of JavaScript.</p><h3>What is TypeScript?</h3><p>TypeScript is a new programming language released by Microsoft in October 2012 after two years of internal development and currently being adopted by many organizations worldwide.</p><p>One of the key reasons why Typescript grew quickly in popularity is because it acts as a superset of the already popular JavaScript language, expanding all its existing features with strong static typings.</p><p>Being a superset of JavaScript means that a valid JavaScript program is also a TypeScript program, either on the client or server side, making it easier for developers to get started with TypeScript.</p><h3>Understanding How TypeScript Works</h3><p>The importance and need for static typings in JavaScript is easy to understand to anyone who faces its challenges every day. To learn how to solve that challenge using TypeScript and learn more about its advantages, it’s important to understand how TypeScript works in practice.</p><p>It was mentioned that TypeScript compiles to JavaScript by the TypeScript compiler, but what is this compiler and what does the compilation process look like?</p><p>Everything starts with the tsconfig.json configuration file that must be placed in the project’s root folder. This file defines options that the compiler needs to use during the compilation process. The good thing is that you don’t need to specify most of the options by yourself. The <a href="https://github.com/tsconfig/bases">GitHub tsconfig bases repository</a> has great configuration examples for most of the environments. You can simply extend them in your tsconfig.json and focus on configuring values specific to your project.</p><p>The next step is to install the TypeScript compiler and compile your TypeScript code to JavaScript. Before doing that, you need to know whether you are going to install it locally or globally in your machine. Depending on the chosen way, the path to the compiler in package.json might need to be adjusted.</p><p>You can either install locally (adding to dev dependencies) using the command yarn add -D typescript or globally using the command yarn global add typescript</p><p>To compile TypeScript files to JavaScript, run the tsc command if you installed the compiler globally or $(npm bin)/tsc otherwise.</p><blockquote>Important note: In the next chapters we will assume that TypeScript was installed globally. If you want to proceed with the local installation, make sure to create a new script in package.json file and use it by executing yarn build:</blockquote><pre>“scripts”: {<br>   “build”: “tsc”,<br>},</pre><blockquote>Remember that package.json automatically loads the contents of the $(npm bin) folder, so it is not necessary to specify the full path to TypeScript compiler (i.e.: $(npm bin)/tsc), but simply tsc should be enough.</blockquote><h3>Creating a simple Typescript application</h3><p>Don’t be overwhelmed by the number of available options in tsconfig.json, it’s always best to start with a simple example and learn the other options along the way.</p><p>Let’s create a simple TypeScript application and compile it to JavaScript!</p><p>The starting point for the compilation process is to create and define the tsconfig.json configuration file, but we don’t have to start from an empty file. The command tsc --init enables us to generate a configuration file with default values and lets the compiler automatically use it.</p><p>After executing the command in the root folder of the project, check the console output for the following message: “Successfully created a tsconfig.json file.” and confirm that a tsconfig.json file was created.</p><p>Open the tsconfig.json file and check its contents. There are several predefined values commented out, but we can also notice some that are active, so let’s figure out what they mean:</p><ul><li>`<a href="https://www.typescriptlang.org/tsconfig#compilerOptions">compilerOptions</a>` — the top-level configuration option that defines how a TypeScript compiler should behave</li><li>`<a href="https://www.typescriptlang.org/tsconfig#target">target</a>` — ECMAScript version our TypeScript code will be compatible with. In case if the code is targeted for all modern browsers, setting `es6` is recommended (so let’s change our `tsconfig.json` to match this), but if the code will be deployed to older environments, it is possible to use `es5` as well. Default value for this setting is `es3`. To use the highest available version, provide `esnext`</li><li>`<a href="https://www.typescriptlang.org/tsconfig#module">module</a>` — sets the module system for the application, recommended option is `commonjs`. Default value for this setting is `commonjs` if `target` is `es3` or `es5`, `es6/es2015` otherwise</li><li>`<a href="https://www.typescriptlang.org/tsconfig#esModuleInterop">esModuleInterop</a>` — emits more JavaScript to ease support for importing CommonJS modules. Default value is `false`</li><li>`<a href="https://www.typescriptlang.org/tsconfig#forceConsistentCasingInFileNames">forceConsistentCasingInFileNames</a>` — force TypeScript to issue an error when an application includes a file with a different casing than on the disk. E.g., if the file is named `DateService.ts` and it is tried to be imported as a `dateService.ts`. Default value is `false`</li><li>`<a href="https://www.typescriptlang.org/tsconfig#strict">strict</a>` — enables stronger type checking behavior</li><li>`<a href="https://www.typescriptlang.org/tsconfig#skipLibCheck">skipLibCheck</a>` — skip type checking of declaration files. Default value is `false`</li></ul><p>Congratulations on getting familiar with the most important configuration options of the TypeScript compiler! Next, let’s write our first TypeScript code sample.</p><h3>Writing your first lines of Typescript code</h3><p>The next step is to write a few lines of code with TypeScript and successfully compile them to JavaScript, so let’s create a file named userService.ts in the root folder of the project and populate it with the following code:</p><pre>interface User {<br>   firstName: string;<br>   lastName: string;<br>}</pre><pre>const getFullName = (user: User) =&gt; `${user.firstName} ${user.lastName}`;</pre><p>The code defines a function named getFullName that takes a user object as the only argument and returns the full name of the user by combining the first and last names.</p><p>After the file is created, we can use the TypeScript compiler to automatically generate JavaScript code based on this example. Assuming you installed globally, execute the tsc command (without any arguments).</p><p>Notice that a new file named userService.js has just in the project’s root directory. This is what the generated JavaScript code looks like for the above TypeScript example:</p><pre>“use strict”;</pre><pre>var getFullName = function (user) { return user.firstName + “ “ + user.lastName; };</pre><p>One important thing to understand before we continue further is how the compiler finds the configuration tsconfig.json file.</p><p>The compiler was able to find the configuration file even though we haven’t provided any argument to the tsc command. This happens because the compiler searches for a valid tsconfig.json file in the current directory. If not found, it continues searching for one across its parent directories. However, it is also possible to specify the path to the tsconfig.json file by adding `-p` flag to the `tsc` command in the following format: `tsc -p /path/to/tsconfig.json`</p><p>What if we have more than a single file to be compiled? Naturally, we are not limited to having our TypeScript code in a single file. The same compiler configuration file tsconfig.json can be used holistically across the entire project.</p><p>Let’s create a second TypeScript code file named projectService.ts with the following content:</p><pre>interface Project {<br>   id: number;<br>   name: string;<br>};</pre><pre>const projects: Project[] = [<br>   {<br>      id: 1,<br>      name: “Project #1”,<br>   },<br>   {<br>      id: 2,<br>      name: “Project #2”,<br>   },<br>];</pre><pre>const getProjectName = (projectId: number) =&gt; projects.find((project) =&gt; project.id === projectId);</pre><p>After running tsc this TypeScript code is compilated to JavaScript and stored in a new file named projectService.js.</p><pre>“use strict”;</pre><pre>const projects = [<br>   {<br>      id: 1,<br>      name: “Project #1”,<br>   },<br>   {<br>      id: 2,<br>      name: “Project #2”,<br>   },<br>];</pre><pre>const getProjectName = (projectId) =&gt; projects.find((project) =&gt; project.id === projectId);</pre><p>Note that running tsc without any arguments compiled all `.ts` files in the directory. Therefore, if we make a change in a file that has already been compiled, that will be reflected in the generated `.js` file after a new compilation.</p><p>Alternatively, it is possible to compile specific TypeScript files by passing a list of files as tsc parameters such as:</p><p>tsc userService.ts or tsc userService.ts projectService.ts</p><p>Another possibility in case there are many files in the project would be to define which files should be compiled in the tsconfig.json configuration file, such as:</p><pre>{<br>   “compilerOptions”: {<br>      // all generated options here<br>   },<br>   “files”: [<br>      “userService.ts”,<br>      “projectService.ts”<br>   ]<br>}</pre><h3>Handling Code Dependencies</h3><p>When our TypeScript code has imports declared inside of the source code file that are not specified in the tsconfig.json configuration file, the TypeScript compiler will automatically include them in the process. As an example, if the projectService.ts imports something from another source file (e.g., coreService.ts), that will also be included in the compilation process.</p><p>Instead of including all files one by one, an industry best practice is to add the files to a separate folder (e.g., src) and instruct the compiler to compile only the files in this directory.</p><p>Next, we will create the `src` folder in our project’s root directory and move both the userService.ts and projectService.ts files to it.</p><p>We can now change our configuration to compile only the files in this folder by using the `include` configuration option (don’t forget to remove the previously used `files` section before doing this):</p><pre>{<br>   “compilerOptions”: {<br>      // all generated options here<br>   },<br>   “include”: [<br>      “src/*”<br>   ]<br>}</pre><p>The inverse scenario, excluding files or folders rather than including them, is also possible by using the `exclude` configuration option as shown in this example:</p><pre>{<br>   “compilerOptions”: {<br>      // all generated options here<br>   },<br>   “include”: [<br>      “src/*”<br>   ],<br>   “exclude”: [<br>      “src/userService.ts”<br>   ]<br>}</pre><p>As you can see, the configuration file gives a tremendous amount of flexibility to manage what files should (or not) be part of the compilation process. However, it is equally important to define how the output should be handled.</p><p>Up until this point, all compiled files were put in the same directory where the original TypeScript file was stored.</p><p>As the codebase grows it will be hard to manage this mix of files within the same directory. A good practice is to place the compiled files to a new directory to keep them separated from the main code. This can be achieved by specifying the `outDir` configuration option inside of the `compilerOptions` in the tsconfig.json file:</p><pre>{<br>   “compilerOptions”: {<br>      // all generated options here<br>      “outDir”: “dist”<br>   }<br>}</pre><p>Run the tsc command now and notice how all generated files are now placed inside of the `dist` directory automatically.</p><p>If you are using git (or other version control system), don’t forget to add the `dist` folder to the .gitignore file to make sure it’s not pushed to the remote repository.</p><h3>Next Steps in Your Learning Journey</h3><p>While there is still much more to learn about TypeScript, its compilation process and possible configuration options, we have now gone through the most important things you need to know to get started with TypeScript.</p><p>This article gave you the foundation to understand what TypeScript is, why it’s important and how you can write TypeScript code and compile it to JavaScript. The compiler configuration options we explored enabled you to organize your code according to industry’s best practices and customize it to better fulfill your requirements.</p><p>As a next step in your learning journey, we recommend you explore the different TypeScript interfaces and types, and of course, keep experimenting with the code! To learn more about TypeScript please <a href="https://www.typescriptlang.org/docs/">visit the official documentation and guidelines</a> page.</p><p>Stay tuned for our next article!</p><h3>About the Author:</h3><p><a href="https://www.linkedin.com/in/volodymyr-hudyma-98bb78131/">Volodymyr Hudyma</a>, Software Engineer at <a href="https://medium.com/fortum-tech">Fortum</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/200/0*ihmmKG9oazeicK31" /><figcaption>Volodymyr Hudyma</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a2cec0e14764" width="1" height="1" alt=""><hr><p><a href="https://medium.com/fortum-tech/what-is-typescript-and-why-would-i-use-it-in-place-of-javascript-a2cec0e14764">What is TypeScript and why would I use it in place of JavaScript?</a> was originally published in <a href="https://medium.com/fortum-tech">Fortum Technology Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[AWS re:Invent 2021: What to expect? Predictions from the Fortum Tech Community]]></title>
            <link>https://medium.com/fortum-tech/aws-re-invent-2021-what-to-expect-predictions-from-the-fortum-tech-community-e95763c64d52?source=rss----32e6561fae3b---4</link>
            <guid isPermaLink="false">https://medium.com/p/e95763c64d52</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[software-architecture]]></category>
            <category><![CDATA[data]]></category>
            <category><![CDATA[cloud]]></category>
            <dc:creator><![CDATA[Bruno Amaro Almeida]]></dc:creator>
            <pubDate>Fri, 26 Nov 2021 16:30:42 GMT</pubDate>
            <atom:updated>2021-11-29T07:41:06.381Z</atom:updated>
            <content:encoded><![CDATA[<h3>AWS re:Invent 2021: What to Expect? Predictions from the Fortum Tech Community</h3><p>The annual AWS event (or as AWS would call it — learning conference), aka re:Invent is almost knocking at the door. This AWS re:Invent edition marks its 10-year anniversary and it’s a return to a Las Vegas in-person format after a two-year gap.</p><p>Traditionally, AWS has been using this yearly event as a platform for releasing new services and major updates. The bar is always very high, and we expect this year won’t be any different! Like millions of AWS experts around the globe, the Fortum Tech community is also eagerly waiting for the event.</p><p>Here are some of the AWS re:Invent predictions and wishes from a few of our Fortum technology experts.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/250/1*y5DwPJzOsRn1zm3SF7t3ig.jpeg" /><figcaption><strong>Sunil Mohanty, Cloud &amp; DevOps Architect</strong></figcaption></figure><h3><strong>Sunil Mohanty, Cloud &amp; DevOps Architect</strong></h3><h4>More services in DevOps space</h4><p>One area where AWS has been lagging with respect to its biggest competitor i.e., Microsoft Azure, is in the DevOps space. After Microsoft acquired GitHub, the feature parity gap in the <a href="https://aws.amazon.com/devops/">AWS DevOps</a> offering has been more visible and it’s now clearly lagging. I would expect several announcements in this domain area.</p><p>On the CI/CD portfolio offering, CodeBuild is a service that has recently seen many good features and updates, and I am a big fan of it! Yet, I wish AWS would improve the AWS CodePipeline service to the same extent. Making it easier to setup and use, in a similar manner to its competitor Github Actions.</p><p>On a similar note, I would not be surprised if AWS announces a project management service, to compete with Atlassian Jira, Github Projects and Microsoft Azure DevOps Projects.</p><h4>On-Premises and Hybrid Cloud</h4><p>AWS has tacitly acknowledged that on-premises infrastructure isn’t going anywhere. At the same time, there is a <a href="https://speaking.brunoamaro.com/vl6qvF/where-organisations-fail-mistakes-misconceptions-about-hybrid-multi-cloud">good demand for multi-cloud services</a>. So, I expect there will be lots of announcements related to the AWS Outposts service, and new products and features with hybrid offerings.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/250/1*vlHU8fyoFSiPT0PDcJ1-fg.jpeg" /><figcaption><strong>Dhaval Vithalani, DevSecOps Technical Lead</strong></figcaption></figure><h3><strong>Dhaval Vithalani, DevSecOps Technical Lead</strong></h3><h4>Enhancements in AWS Data &amp; Analytics</h4><p>Several AWS competitors, such as other public cloud and independent SaaS providers, are spearheading the data and analytics space in terms of advanced services and innovation. Last year, data companies like Snowflake, were able to capture market share by solving big and complex problems with cloud data warehousing solutions that are incredibly scalable, faster and cloud vendor agnostic. These solutions are also paving the way when it comes to data security and access management across organizations. Moreover, a big portion of data scientists and analysts in the enterprise world are today inclining towards technologies such as Azure Data Lake and Power BI for their data processing, analytics and business intelligence needs.</p><p>In this AWS re:Invent, I expect that AWS will bring several improvements in terms of scalability and compute decoupling (in AWS RedShift), and new services and features that would bring improvements and feature parity in the data domain.</p><h4>Future is Crypto &amp; Blockchain</h4><p>Amazon <a href="https://aws.amazon.com/managed-blockchain/features/?nc=sn&amp;loc=2">Managed Blockchain</a> is a service that will be under the attention of a lot of Cloud Evangelist and business leaders. Personally, I am expecting in this AWS re:Invent the announcement of power optimized AWS GPU instances and the ability to launch virtual machines behind ASIC Hardware. This would have a big impact in helping thousands of blockchain and crypto enthusiasts to build their environments for the development of dApps (Distributed Apps).</p><h4>New services in security aspect of DevOps.</h4><p>Last year AWS <a href="https://aws.amazon.com/about-aws/whats-new/2020/06/amazon-codeguru-now-generally-available/">introduced a static code review tool, Amazon Code Guru Reviewer and Profiler</a>, for SAST matching in line with capabilities of specialized tools such as SonarQube. This year I expect more AWS services and features that would cover other areas of software security such as DAST (Dynamic Application Security Testing), IAST (Interactive Application Security Testing), RAST (Rapid Application Security Testing) and SCA (Software Composition Analysis).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/250/1*uuxS6JP8i18_1qU4faLrpQ.jpeg" /><figcaption><strong>Bruno Amaro Almeida, Head of Technology &amp; Architecture</strong></figcaption></figure><h3><strong>Bruno Amaro Almeida, Head of Technology &amp; Architecture</strong></h3><h4>Making life even easier for serverless cloud-native engineering teams</h4><p>Nowadays it is quite common to find software engineering teams that are cloud-native and fully using AWS managed services. However, I still see <a href="https://speaking.brunoamaro.com/0RW3xc/7-aws-deadly-sins">teams spending a tremendous amount of effort</a> in building integrations across different managed services and producing custom logic to handle high availability and fault tolerance.</p><p>I expect to see AWS announcing several products and features that would provide built-in integrations between their offering and third-party partner services, global and multi-region high availability out of the box, and chaos engineering methods to enable more resilient architecture and drop unnecessary toil created by teams.</p><h4>Welcoming complexity and niche use cases from Enterprise</h4><p>AWS made a big U-turn in the past years by welcoming hybrid and multi cloud scenarios and architectures with services such as AWS Outposts and ECS (Elastic Container Service) &amp; EKS (Elastic Kubernetes Service) Anywhere.</p><p>In the enterprise world, it is still common to find certain workloads that organizations choose not to migrate to any public cloud due to certain constraints such as monolithic solutions, niche use cases, or complex architectures.</p><p>In this AWS re:Invent edition I suspect we will see a few announcements that might seem odd for cloud native engineering teams. Judging by the newly announced AWS RDS (Relational Database Service) Custom — for managing complex self-hosted Oracle databases — these new features will be targeted to a few selected big enterprises and will give them an important nudge towards cloud and managing complexity.</p><h4>Forward looking and innovative features</h4><p>It would not be AWS re:Invent without a few announcements with innovative products and features that cause a stir and push the boundaries of what public cloud looks like today.</p><p>With the recent <a href="https://aws.amazon.com/blogs/quantum-computing/announcing-the-opening-of-the-aws-center-for-quantum-computing/">unveiling of the new AWS Center for Quantum Computing,</a> I think we might see some interesting ideas and concepts being featured at re:Invent that will incentivize people to use and leverage <a href="https://aws.amazon.com/braket/">AWS Braket</a> in their solutions.</p><p>On the same note, with Web 3.0 and dApps (Distributed Apps) recent popularity, I would expect to see some announcements related to that development area and expanding the Amazon Managed Blockchain service offering.</p><p>Along with other AWS Partner Ambassadors and Community Builders, I <a href="https://twitter.com/AWScomsum/status/1463139920021794816?s=20">will be live in the AWS Community Online panel discussion on December 2nd</a> for a coverage of all the new features and announcements. Join us!</p><p>As always, we are looking forward to the surprises this AWS Re:Invent 2021 will bring us!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e95763c64d52" width="1" height="1" alt=""><hr><p><a href="https://medium.com/fortum-tech/aws-re-invent-2021-what-to-expect-predictions-from-the-fortum-tech-community-e95763c64d52">AWS re:Invent 2021: What to expect? Predictions from the Fortum Tech Community</a> was originally published in <a href="https://medium.com/fortum-tech">Fortum Technology Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>