add authentication link to test mode topic #790
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
techcobweb
reviewed
May 8, 2024
|
|
||
| ## <a name="hybrid"></a>Running a test locally but using shared configuration | ||
|
|
||
| When you run a test locally, but using shared configuration, the Galasa bootstrap is set to the URL of the Galasa Ecosystem where the shared configuration is stored. The Galasa framework is launched within the JVM on the local machine, but the framework consults the remote ecosystem to read configuration data, but not the credentials properties as these are drawn from a local file. This is the key difference between running a test in this "hybrid" mode versus running a test locally without using shared configuration. In hybrid mode, the test still runs in the local JVM and all test results and artifacts are stored on the local disk. | ||
| When you run a test locally, but using shared configuration, the Galasa bootstrap is set to the URL of the Galasa Ecosystem where the shared configuration is stored. The Galasa framework is launched within the JVM on the local machine, but the framework consults the remote Ecosystem to read configuration data, but not the credentials properties as these are drawn from a local file. This is the key difference between running a test in this "hybrid" mode versus running a test locally without using shared configuration. In hybrid mode, the test still runs in the local JVM and all test results and artifacts are stored on the local disk. |
There was a problem hiding this comment.
the Galasa bootstrap is set to the URL of the Galasa Ecosystem where the shared configuration is stored
Currently that's not true. You need to galasactl auth login to the remote system (which does require a bootstrap), and then unset the bootstrap so that your local bootstrap.properties file is used. Or refer explicitly to the local bootstrap file.
There was a problem hiding this comment.
0.34.0 Contains a change such that it will do an implicit login, so you don't actually need to login explicitly now.
There was a problem hiding this comment.
will chat to you about the implicit login changes
techcobweb
reviewed
May 8, 2024
| - `https://my.ecosystem.url` refers to the Web UI used to allocate tokens and <br> | ||
| - `framework.extra.bundles` tells the Galasa framework to load the `dev.galasa.cps.rest` extension. This extension tells the Galasa framework how to handle URLs that start with `galasacps` as the *scheme* part of the URL. <br> | ||
|
|
||
| After setting the `GALASA_TOKEN` to be a valid token for the Ecosystem from which the CPS property values will be drawn, you can run a test in hybrid mode by setting your bootstrap to refer to the Ecosystem in which the shared configuration is stored, and using the `galasactl runs submit local` <a href="https://github.com/galasa-dev/cli/blob/main/docs/generated/galasactl_runs_submit_local.md" target="_blank"> Galasa CLI</a> command. |
There was a problem hiding this comment.
After setting the
GALASA_TOKENto be a valid token for the Ecosystem from which the CPS property values will be drawn,
... log into the Ecosystem using galasactl auth login
Then
you can run a test in hybrid mode by setting your bootstrap to refer to the Ecosystem in which the shared configuration is stored,
techcobweb
previously approved these changes
Jun 3, 2024
| @@ -20,13 +20,18 @@ There are three modes in which you can run a Galasa test:<br><br> | |||
| - remotely, by submitting the test to run in the Galasa Ecosystem<br> | |||
|
|
|||
|
|
|||
| If you are running a test locally but using a shared configuration that is hosted by the Galasa Ecosystem, or running a test remotely by submitting the test to run in the Galasa Ecosystem, you are interacting with the Galasa Ecosystem. | |||
|
|
|||
| Before you can interact with the Galasa Ecosystem, you must authenticate with it by using a personal access token. Tokens are stored in the `GALASA_TOKEN` in the `galasactl.properties` in your Galasa home folder. You can request a personal access token by using the Galasa Web UI. For more information about setting up authentication with an Ecosystem, see the [Configuring authentication](../ecosystem/ecosystem-authentication) documentation. | |||
There was a problem hiding this comment.
You can also store the token in an environment variable $GALASA_TOKEN
|
|
||
| ## <a name="hybrid"></a>Running a test locally but using shared configuration | ||
|
|
||
| When you run a test locally, but using shared configuration, the Galasa bootstrap is set to the URL of the Galasa Ecosystem where the shared configuration is stored. The Galasa framework is launched within the JVM on the local machine, but the framework consults the remote ecosystem to read configuration data, but not the credentials properties as these are drawn from a local file. This is the key difference between running a test in this "hybrid" mode versus running a test locally without using shared configuration. In hybrid mode, the test still runs in the local JVM and all test results and artifacts are stored on the local disk. | ||
| When you run a test locally, but using shared configuration, the Galasa bootstrap is set to the URL of the Galasa Ecosystem where the shared configuration is stored. The Galasa framework is launched within the JVM on the local machine, but the framework consults the remote Ecosystem to read configuration data, but not the credentials properties as these are drawn from a local file. This is the key difference between running a test in this "hybrid" mode versus running a test locally without using shared configuration. In hybrid mode, the test still runs in the local JVM and all test results and artifacts are stored on the local disk. |
There was a problem hiding this comment.
0.34.0 Contains a change such that it will do an implicit login, so you don't actually need to login explicitly now.
KirbyKatcher
previously approved these changes
Jun 24, 2024
KirbyKatcher
approved these changes
Jul 17, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.