Describe the bug

Although TypeScript definition files *.d.ts are being bundled within this NPM package, VSCode is not recognizing them for code completion and code insights.

To Reproduce
Steps to reproduce the behavior:

1. Import this repo in a new or existing javascript (browser or node.js) project
2. Open a .js file and declare the usage of this package
3. Type a variable name and then a dot (.)

Expected behavior

The available API services should be suggested and auto completed

Screenshots

Desktop (please complete the following information):

• OS: [e.g. macOS Catalina]

Additional context

Noticed that under <my-project>/node_modules/devopness-sdk-js/dist there are *.d.ts definition files.

Problem: What is happening?

In Linked-resources documentation (Add a Linked Resource topic) have a step that needs be updated.

Step 5 says to click "...", but that button has been replaced by the "settings" button.

Expected behavior

It is expected that step 5 will ask you to click on the "settings" button.

Steps to reproduce

1. On Devopness, navigate to a project then select an environment
2. Find the Applications card
3. Click View in the Applications card to see a list of existing Applications
4. Click DETAILS on the application you want to link a server
5. On the upper-right corner of the application details view, click "..."

The "..." button does not exist.

Which Devopness module(s) are the source of the bug?

Documentation

SDK Version

No response

Reproduction link

No response

Additional details

No response

Description

Article Edit a Pipeline needs to be updated, more details @ #855

Issue List

• Guide the user to click Resource Name
  • Steps below needs to be fixed accordingly

  1. In the list of applications find the application with the pipeline you want to edit and click DETAILS
  1. In the list of pipelines find the pipeline you want to edit and click DETAILS
  

• Guide the user to use Tabs
  • Steps below needs to be fixed accordingly

  1. On the upper-right corner of the applications details view click SETTINGS
  1. Use the drop-down menu to choose PIPELINES
  

Description

Article Edit an Application needs to be updated, more details @ #855

Issue List

• Guide the user to click Resource Name
  • Steps below needs to be fixed accordingly

  1. Click DETAILS on the application you want to edit
  

Description

Article Edit a File needs to be updated, more details @ #855

Issue List

• Guide the user to click Resource Name
  • Steps below needs to be fixed accordingly

  1. In the list of applications find the application with the configuration file you want to edit and click DETAILS
  1. In the list of configuration files find the configuration file you want to edit and click DETAILS
  

• Guide the user to use Tabs
  • Steps below needs to be fixed accordingly

  1. On the upper-right corner of the applications details view click SETTINGS
  1. Use the drop-down menu to choose CONFIGURATION FILES
  

• Use correct resource type name
  • ❌ On the upper-right corner of the key details, click EDIT
  • ✅ On the upper-right corner of the configuration file details, click EDIT

Description

Article Add a Pipeline needs to be updated, more details @ #855

Issue List

• Guide the user to click Resource Name
  • Step "In the list of applications find the application where you want to add a pipeline and click DETAILS" needs to be fixed accordingly
• Guide the user to use Tabs
  • Steps below needs to be fixed accordingly

  1. On the upper-right corner of the applications details view click SETTINGS
  1. Use the drop-down menu to choose PIPELINES
  1. On the right corner of the list click ADD PIPELINE
  

Description

Article Remove a Self Hosted Server needs to be updated, more details @ #855

Issue List

• Guide the user to click Resource Name
  • Steps below needs to be fixed accordingly

  1. In the list of servers, find the server you want to remove and click DETAILS
  

Is your feature request related to a problem? Please describe.

No response

Describe the solution you'd like.

Today it only allows you to create an application with nodejs 12 or 16. Some applications like nextjs 14 only work on the latest version of nodejs

Additional context

No response

Description

Article Add an SSL Certificate needs to be updated, more details @ #855

Issue List

• Guide the user to click Resource Name
  • Steps below needs to be fixed accordingly

  1. Click DETAILS on the application you want to add an SSL certificate to
  

• Guide the user to find labels instead of icons
  • It is preferable to not have a UI dependency inside the documentation
  • The documentation, in the current state, will need an update for every icon change

  1. On the upper-right corner click SSL (open lock icon)
  

• Guide the user on what action to expect when deploying an ssl certificate, similar to other articles that trigger actions
  • ❌ An action to install the SSL certificate will start
  • ✅ Wait for the ssl-certificate:deploy action to be completed

Description

Article Add a Subnet needs to be updated, more details @ #855

Issue List

• Guide the user to click Resource Name
  • Steps below needs to be fixed accordingly

  1. In the list of networks, find the network you want to manage and click DETAILS
  

Description

Article Deploy Application using an Incoming Hook needs to be updated, more details @ #855

Issue List

• Guide the user to click Resource Name
  • Steps below needs to be fixed accordingly

  1. In the list of applications, find the application with the pipeline you want to manage and click DETAILS
  1. In the list of pipelines, find the pipeline you want to manage and click DETAILS
  1. Click DETAILS on the application you triggered the pipeline
  

• Guide the user to use Tabs
  • Steps below needs to be fixed accordingly

  1. On the upper-right corner of the applications details view click SETTINGS
  1. Use the drop-down menu to choose PIPELINES
  

• Update text to show <pipeline_id> as text
  • ❌ Steps to find the `` of an application:deploy pipeline
  • ✅ Steps to find the pipeline_id of an application:deploy pipeline

Problem: What is happening?

When I attempt to delete a server that has not had its deployment completed, the system does not allow the action to be completed. However, no message is reported on the screen explaining why the action is not accepted.

Upon reviewing the logs in DevTools, it appears that the reason is as follows:

"Operation not allowed: Could not delete server '' with status 'pending'. Only 'stopped' or self-hosted servers can be removed. Please, stop the server before deleting it."

However, none of the actions (Start, Stop, Restart) work, thus making it impossible to remove this defective server from the platform.

Expected behavior

When a server fails to complete its deployment for any reason, there should be the capability to DELETE the server from the system, preventing a non-functional item from remaining on the dashboard.

Steps to reproduce

1. Set up a server.
2. Introduce an error (such as invalid credentials) that prevents the Deployment from being completed.
3. Attempt to delete the server.

Which Devopness module(s) are the source of the bug?

Devopness API, Devopness web app

SDK Version

No response

Reproduction link

No response

Additional details

No response

Describe the solution you'd like
Include a mechanism to specify the API version used by the SDK.

The default API version would be the latest, but users would be able to specify a previous version. This would be specially useful to maintain backwards compatibility, at least on a reasonable timeframe for users to update their code.

Describe alternatives you've considered
Including this feature later, when a breaking API version comes along.

Which Devopness module(s) are the source of the bug?

Devopness web app

SDK Version

No response

Expected behavior

Once I click on "Remove" on the pipeline step, the removal confirmation page should show up so I can remove it.

What is actually happening?

Once I click on "Remove" on the pipeline step, the page either doesn't show and redirects back to the "Projects" page or shows very briefly and the redirects to the "Projects" page.

Reproduction link

No response

Steps to reproduce

1. Go to an application you've created or have permissions to add steps to it's pipeline.
2. Click on "Details".
3. Click on the dropdown menu named "Settings".
4. Click on "Pipelines".
5. Choose a pipeline by clicking on it's corresponding "Details" button.
6. Click on "Steps".
7. If there are no previously created steps, create one.
8. Click on "Remove" on a created pipeline step.

Additional details

This behavior has been reproduced in the browsers:

• Firefox 120.0
• Chromium 119.0.6045.199

Description

Article Remove an SSH Key needs to be updated, more details @ #855

Issue List

• Guide the user to click Resource Name
  • Steps below needs to be fixed accordingly

  1. In the list of keys, find the key you want to remove and click DETAILS
  

Which Devopness module(s) are the source of the bug?

Devopness web app

SDK Version

No response

Expected behavior

I should be able to remove a server that was not successfully provisioned because of some incorrect configuration.

What is actually happening?

I am unable to remove the server.

Reproduction link

No link

Steps to reproduce

1. Add a new server
2. Select a cloud provider
3. Select an invalid credential
4. Select a region
5. Select an instance type
6. Select an OS version
7. Confirm choices and wait for server provision to fail. "Check provisioned" status should fail
8. Click on "..." -> "Remove" and try to remove server. It should fail saying a server must be on status "Stopped" to be removed.
9. Click on "Actions" dropdown menu and try to stop server. It should fail.
10. Click on "Actions" dropdown menu and click on "Status", the "Get Status" action should fail.

Additional details

No response

Description

Article Remove Step from Pipeline needs to be updated, more details @ #855

Issue List

• Guide the user to click Resource Name
  • Steps below needs to be fixed accordingly

  1. In the list of applications, find the application with the pipeline you want to manage and click DETAILS
  1. In the list of pipelines, find the pipeline you want to manage and click DETAILS
  

• Guide the user to use Tabs
  • Steps below needs to be fixed accordingly

  1. On the upper-right corner of the application details view, click SETTINGS
  1. Use the drop-down menu to choose PIPELINES, to see a list of existing Pipelines
  

Description

Article Remove a Subnet needs to be updated, more details @ #855

Issue List

• Guide the user to click Resource Name
  • Steps below needs to be fixed accordingly

  1. In the list of networks, find the network with the subnet you want to remove and click DETAILS
  1. In the list of subnets, find the subnet you want to remove and click DETAILS
  

Discussed in #843

Description

Article Get a Server’s Status needs to be updated, more details @ #855

Issue List

• Guide the user to click Resource Name
  • Steps below needs to be fixed accordingly

  1. In the list of servers, find the server you want to inspect and click DETAILS
  

• Update action code to lowercase
  • ❌ Wait for the Server:Get-status action to be completed
  • ✅ Wait for the server:get-status action to be completed

Description

Article Restart a Server needs to be updated, more details @ #855

Issue List

• Guide the user to click Resource Name
  • Steps below needs to be fixed accordingly

  1. In the list of servers, find the server you want to restart and click DETAILS
  

• Update action code to lowercase
  • ❌ Wait for the Server:restart action to be completed
  • ✅ Wait for the server:restart action to be completed

Description

Article Add a File needs to be updated, more details @ #855

Issue List

• Guide the user to click Resource Name
  • Steps below needs to be fixed accordingly

  1. In the list of applications find the application where you want to add a configuration file and click DETAILS
  

• Guide the user to use Tabs
  • Steps below needs to be fixed accordingly

  1. On the upper-right corner of the applications details view click SETTINGS
  1. Use the drop-down menu to choose CONFIGURATION FILE
  1. On the right corner of the list click ADD CONFIGURATION FILE
  

Problem: What is happening?

When trying to delete a server that has already been deleted by the digital ocean platform, devopness asks to stop the server as shown in the image.

Expected behavior

remove server

Steps to reproduce

1. go to delete server

error "Operation not allowed: Could not delete server 'rifaweb-rifaweb-m5' with status 'running'. Only 'stopped' or self-hosted servers can be removed. Please, stop the server before deleting it."

Which Devopness module(s) are the source of the bug?

Devopness website

SDK Version

No response

Reproduction link

No response

Additional details

No response

Description

Article Archive an Environment and Unarchive an Environment needs to be updated

Archive button moved to Settings

Now, when a user wants to archive/unarchive an environment, they need to click the Settings button and select the option from the dropdown menu, as highlighted in the picture below

Issue List

• Update "Select a project" step

-  1. Select a Project
+  1. In the list of Projects find the Project with the Team you want to manage and click View

• Remove "Find the Environments card" step, removing duplicated step

-  1. Find the Environments card
   1. Click View in the Environments card to see a list of existing Environments

• Guide the user to click SETTINGS

-  1. On the upper-right corner of the Environment resources list, click ...
+  1. On the upper-right corner of the Environment resources list, click SETTINGS

Description

Article Remove a Network needs to be updated, more details @ #855

Issue List

• Guide the user to click Resource Name
  • Steps below needs to be fixed accordingly

  1. In the list of networks, find the network you want to remove and click DETAILS
  

Description

Article Deploy SSH Key needs to be updated, more details @ #855

Issue List

• Guide the user to click Resource Name
  • Steps below needs to be fixed accordingly

  1. Click DETAILS on the SSH key you want to deploy
  

• Update action code to lowercase
  • ❌ Wait for the Ssh-key:Deploy action to be completed
  • ✅ Wait for the ssh-key:deploy action to be completed

Discussed in #837

Description

Article Run a Pipeline needs to be updated, more details @ #855

Issue List

• Guide the user to click Resource Name
  • Steps below needs to be fixed accordingly

  1. Click DETAILS on the network rule you want to run a pipeline
  

• Guide the user to use Tabs
  • Steps below needs to be fixed accordingly

  1. On the upper-right corner of the network rule details view, click SETTINGS
  1. Use the drop-down menu to choose PIPELINES, to see a list of existing Pipelines
  

• Update action code to lowercase
  • ❌ Wait for the action Network-rule:Deploy to be completed
  • ✅ Wait for the action network-rule:deploy to be completed

Description

Article Check a Role's Permissions needs to be updated, more details @ #855

Issue List

• Guide the user to click Resource Name
  • Steps below needs to be fixed accordingly

  1. In the list of Roles find the Role you want to check the permissions and click DETAILS
  

Description

Article Stop a Server needs to be updated, more details @ #855

Issue List

• Update public IP address note to warning
• Guide the user to click Resource Name
  • Steps below needs to be fixed accordingly

  1. In the list of servers, find the server you want to stop and click DETAILS
  

• Update action code to lowercase
  • ❌ Wait for the Server:stop action to be completed
  • ✅ Wait for the server:stop action to be completed

Is your feature request related to a problem? Please describe.

Dependencies might be update very often, and keep them up to date is hard, a way to be notified mainly for security fixes will be very helpful.

Describe the solution you'd like

Setting up dependabot on this repo will ensure we're notified through pull requests (that we can decide do merge or close) every time a dependency releases a new version on npm.

Additional context

Article on how to set up dependabot:
https://github.com/marketplace/dependabot-preview

Discussed in #918

Description

Article Add member needs to be updated

Team Details page created

Now, when the user clicks to view a Team, they are redirected to the team details page with 2 subresources: INVITATIONS and MEMBERS, as highlighted in the picture below

To guide the user to add a member to a team, now there's an extra step: click INVITATIONS (or MEMBERS)

Add Member renamed Invite Member

Invitations and Members are separated subresources on the UI, so now it's more clear what the result of submitting "Add member" form is: a Team invitation. With that, came the decision to update the label to Invite Member

Issue List

• Update "Select a project" step

-  1. Select a Project
+  1. In the list of Projects find the Project with the Team you want to manage and click View

• Update "Find the Teams card" step

-  1. Find the Teams card
+  1. Click View in the Teams card to see a list of existing Teams

• Guide the user to click INVITATIONS

  1. Click View in the Teams card to see a list of existing Teams
  1. In the list of Teams find the Team you want to add a member and click View
+ 1.  On the upper-right corner of the team details view, click INVITATIONS

• Guide the user to click INVITE MEMBER

- 1. On the upper-right corner of the Members list, click ADD MEMBER
+ 1. On the upper-right corner of the Invitations list, click INVITE MEMBER

• Fix typo

- 1. Provide the email of the member to be invites
+ 1. Provide the email of the member to be invited

• Rename article to "Invite Team Member"
• Move article to docs/teams/invitations/add-invitation
• Update next link on Add a Team
• Update previous link on Add team membership

Description

Article Remove a File needs to be updated, more details @ #855

Issue List

• Guide the user to click Resource Name
  • Steps below needs to be fixed accordingly

  1. In the list of applications, find the application with the configuration file you want to remove and click DETAILS
  1. In the list of configuration files, find the file you want to remove and click DETAILS
  

• Guide the user to use Tabs
  • Steps below needs to be fixed accordingly

  1. On the upper-right corner of the applications details view, click SETTINGS
  1. Use the drop-down menu to choose CONFIGURATION FILES, to see a list of existing Configuration Files
  

Is your feature request related to a problem? Please describe.

Although this repository already have server side github checks validating incoming pull requests, having a simple way to ensure a build runs before a pushing local changes to remote might speed up error detection.

Describe the solution you'd like

• Add a pre-push hook file git-push.sh file to the repository and ensure it can be copied by .git/hooks directory on cloning.
• Add a setup script to copy hook files to .git/hooks directory

Describe alternatives you've considered

Might be simpler to just use git templates instead of defining a setup script. Some research might be needed to investigate what are current best practices on the matter.

Additional context

Description

Article Start a Server needs to be updated, more details @ #855

Issue List

• Guide the user to click Resource Name
  • Steps below needs to be fixed accordingly

  1. In the list of servers, find the server you want to start and click DETAILS
  

• Update action code to lowercase
  • ❌ Wait for the Server:start action to be completed
  • ✅ Wait for the server:start action to be completed

Problem: What is happening?

the pipeline is breaking because it doesn't find the version of node.js:16.16, but it is configured in the application as shown in the image.

The error message below says that the version of node.js16.16 was not found, but it was configured correctly in the application.

Expected behavior

It was expected that the pipeline would find the node.js version and not break

Steps to reproduce

CLICK ON IN THE TOP RIGHT CORNER ADD APPLICATION
FILL IN THE FIELDS OF YOUR SOURCE PROVIDER
CHOOSE THE NODEJS STACK
select engine version: 16.16
Define your repository's directory layout
Define build configuration
CLICK NEXT
RETURN TO APPLICATIONS PAGE
CLICK ON 'DEPLOY'
SELECT THE PERTINENT PIPELINE
CLICK ON RUN DEPLOY

see error when installing dependencies

Which Devopness module(s) are the source of the bug?

Don't know / other

SDK Version

No response

Reproduction link

my link reproduction: https://app.devopness.com/actions/20803

Additional details

No response

Is your feature request related to a problem? Please describe.

No response

Describe the solution you'd like.

Currently, an environment can only be archived, which makes it read-only and does not remove any of it's linked resources. I believe that in cases where an environment is empty (no linked resources) it would be useful if it could be removed.

Additional context

No response

Is your feature request related to a problem? Please describe.

Currently SDK users need to implement a token refresh process if they want to keep a user logged in. This works fine, but could be easier for SDK users when a token expired, as token expiration HTTP 401 may require some logic to be differentiated from regular HTTP 401 status code.

Describe the solution you'd like

Describe alternatives you've considered

Check for HTTP status code equals 401 and send a token refresh request.

Pseudo-code, yet to be tested:

    public onTokenExpired: () => void;

    public tokenExpired(): void {
        if (this.onTokenExpired) {
            this.onTokenExpired();
        }
    }

Additional context

The responsibility on making the decision of refreshing a token or not doesn't change. It'll still be up to the SDK consumer to decide what to do.
We just want to assume the logic that will check the HTTP 401 Unauthorized response to tell which ones are related to token expiration and notify the client app.

Is your feature request related to a problem? Please describe.

Improve the sample source code provided for first time users of this SDK.

Describe the solution you'd like

Make it easier for users to understand how to consume this package in the most common scenarios:

• CLI: Node.js
• Server side: Node.js
• Browser, from CDN: Javascript
• Browser, from NPM: Javascript
• Browser, from NPM: Typescript with Parcell or webpack

Describe alternatives you've considered

Use codesandbox.io, runkit.com or related tools that allow running the sample code online.

Additional context

Description

This issue aims to list all documentation articles that need to be reviewed after the recent updates in the web app have changed the user flows considerably

Task List

• #859
• #860
• #861
• #862
• #863
• #864
• #865
• #858
• #866
• #867
• #868
• #869
• #870
• #871
• #872
• #873
• #874
• #875
• #876
• #877
• #878
• #879
• #880
• #856
• #881
• #882

Details Button replaced with Details link

Pages that listed resources (e.g: Applications) had a button on labeled DETAILS to access a resource details page (e.g: Application Details), as mentioned in the article quoted below from the documentation available @ Add a File

4. In the list of applications find the application where you want to add a configuration file and click DETAILS

The DETAILS button was replaced by a link in the resource name column

Articles that need to be updated

All articles that guide the users to search for DETAILS button on the UI

Linked Resources replaced with Tabs

A link between resources like Applications and Servers was managed using the Linked Resources page, this was replaced by adding tabs to the Application Details page; this way eliminating the concept of Linked Resources from the app

Articles that need to be updated

All articles related to Linked Resources, Configuration Files and Variables need to be updated

Update Table

This table tracks all documentation articles and lists if the article is updated according to each category below:

• Details: Does this article guide users to the DETAILS link instead of the DETAILS button?
• Tabs: Does this article guide users to use the tabs instead of the linked resource, pipelines, variables, configuration files pages ?

And the column data can be one of the possibilities below:

1. An empty means the article is not affected by that change
2. An ❌ emoji means the article has an issue related to that change
3. An ✅ emoji means the article does not have an issue related to that change

Description

Article Add Step to Pipeline needs to be updated, more details @ #855

Issue List

• Guide the user to click Resource Name
  • Steps below needs to be fixed accordingly

  1. In the list of applications find the application with the pipeline you want to manage and click DETAILS
  1. In the list of pipelines, find the pipeline you want to manage and click DETAILS
  

• Guide the user to use Tabs
  • Steps below needs to be fixed accordingly

  1. On the upper-right corner of the applications details view click SETTINGS
  1. Use the drop-down menu to choose PIPELINES
  

Description

Article Delete a Server provisioned by Devopness needs to be updated, more details @ #855

Issue List

• Guide the user to click Resource Name
  • Steps below needs to be fixed accordingly

  1. In the list of servers, find the server you want to delete and click DETAILS
  

Problem: What is happening?

When an incorrect secret for a cloud provider is entered, the system does not provide any feedback. This impacts the user experience as they are left unsure if the operation was successful or not.

Expected behavior

When an incorrect secret is entered, the system should provide a clear and concise error message like an alert, informing the user about the incorrect secret.

Steps to reproduce

1. Go to the "Cloud Providers"
2. Click on "ADD CLOUD PROVIDER"
3. Select "Amazon Web Services"
4. Click on "NEXT"
5. Enter any name in the name field
6. Enter a valid access key in the access key field
7. Enter an incorrect secret in the secret field
8. Click on "CONFIRM"
9. Observe that no feedback is provided to the user.

Which Devopness module(s) are the source of the bug?

Devopness website

SDK Version

No response

Reproduction link

No response

Additional details

The application attempts to communicate with AWS to verify the correctness of the secret. If the secret is incorrect, it fails silently without providing any feedback to the user. The API does return an error when the secret is incorrect, but this error is not displayed to the user, so it's a front-end issue. Below is an image justifying the return of the API:

No response

Description

Article Add a Linked Resource needs to be updated, more details @ #855

Issue List

• Guide the user to click Resource Name
  • Steps below needs to be fixed accordingly

  1. Click DETAILS on the application you want to link a server
  

• Guide the user to use Tabs
  • Note below needs to be fixed accordingly

  Clicking the LINK TO dropdown will list all available options of resource types to be linked to the selected resource
  

  • Steps below needs to be fixed accordingly

  1. On the upper-right corner of the application details view, click SETTINGS
  1. Use the drop-down menu to choose Linked resources
  1. On the upper-right corner of the Linked resources list, click LINK TO
  1. Use the drop-down menu to choose Servers
  1. Follow the prompts then click Link
  1. In the Linked Resource list, the recently linked server can be seen in the DEPENDS ON table
  

• Rename article to "Link a server to an application"
• Move article to docs/applications folder
• Delete docs/linked-resources folder
• Update next link on Add a File
• Update previous link on Deploy Application
• Update mentionPost usage to point to the new article path
  • E.g:

    devopness/docs/pipelines/run-pipeline.md

    Line 36 in 575dc3b

    If there are no servers linked to the network rule, follow the guide {% mentionPost "/docs/linked-resources/add-linked-resource" %}

Description

Article Remove a Pipeline needs to be updated, more details @ #855

Issue List

• Guide the user to click Resource Name
  • Steps below needs to be fixed accordingly

  1. In the list of applications, find the application with the pipeline you want to remove and click DETAILS
  1. In the list of pipelines, find the pipeline you want to remove and click DETAILS
  

• Guide the user to use Tabs
  • Steps below needs to be fixed accordingly

  1. On the upper-right corner of the application details view, click SETTINGS
  1. Use the drop-down menu to choose PIPELINES, to see a list of existing Pipelines
  

Npmjs supports scoped packages like @devopness/devopness-sdk-js. This enforces your brand and allow you to expand to private repositories easily when it would be required.

Suggestion: create a private free organization in Npm and publish this package again.

Is your feature request related to a problem? Please describe.

No response

Describe the solution you'd like.

I want to be able to remove a project that I have created.

Additional context

No response

Which Devopness module(s) are the source of the bug?

SDK-JS

SDK Version

2.115.0

Expected behavior

As a SDK user, i expected that the StaticService class should have a serverOptions property

What is actually happening?

StaticService doesn't have a serverOptions property

Reproduction link

https://github.com/devopness/devopness/blob/7344938b224e461ce488e0496890389dc59baeab/packages/sdks/javascript/src/services/StaticService.ts#L13C1-L25C2

Steps to reproduce

1. Instantiate DevopnessApiClient.

const devopnessApi = new DevopnessApiClient({ baseURL: BASE_URL })

2. Try access devopnessApi.static.serverOptions
3. See that serverOptions property doesn't exists

Additional details

No response

Description

Article Link an SSH Key to a Server needs to be updated, more details @ #855

Issue List

• Guide the user to click Resource Name
  • Steps below needs to be fixed accordingly

  1. Click DETAILS on the SSH key you want to link to a server
  

• Guide the user to use Tabs
  • Steps below needs to be fixed accordingly

  1. On the upper-right corner of the SSH key details view, click SETTINGS
  1. Use the drop-down menu to choose Linked resources
  1. On the upper-right corner of the Linked resources list, click LINK TO
  1. Use the drop-down menu to choose Servers
  1. Follow the prompts then click Link
  1. In the Linked Resource list, the recently linked server can be seen in the DEPENDS ON table