Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Adding initial getting started wizard content #1878

Open
wants to merge 16 commits into
base: master
Choose a base branch
from

Conversation

alexmolev
Copy link
Contributor

No description provided.

@alexmolev alexmolev marked this pull request as ready for review June 15, 2021 10:18
@alexmolev
Copy link
Contributor Author

alwaysopen = false
+++

OK, so you have your {{< param cfy_manager_name >}} setup ready. When you login to the {{< param cfy_manager_name >}} for first time a getting started wizard is presented.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
OK, so you have your {{< param cfy_manager_name >}} setup ready. When you login to the {{< param cfy_manager_name >}} for first time a getting started wizard is presented.
OK, so you have your {{< param cfy_manager_name >}} setup ready. When you log in to the {{< param cfy_manager_name >}} for the first time, a getting started wizard is presented.


You can select multiple technologies and install all the required resources at once.

Find below the supported technologies, you can find out what resources are installed as part of it by clicking on each one of them:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Find below the supported technologies, you can find out what resources are installed as part of it by clicking on each one of them:
Find below the supported technologies, you can find out what resources are installed per each technology by clicking their link:

![1_getting_started.png]( /images/getting_started/1_getting_started.png )

The wizard will assist you with setting up your {{< param cfy_manager_name >}} with installing plugins, secrets and blueprints.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
- Plugins are {{< param cfy_manager_name >}}’s extendable interfaces to services, cloud providers, and automation tools. E.g., connecting to AWS requires the AWS plugin.
- To interact with the technology (e.g. infrastructure), credentials are required. {{< param cfy_manager_name >}} stores such sensitive information in **secrets**. Secrets are kept encrypted in a secure way and used in run-time by the system. You will be asked to provide the access credentials for the technology you selected.
- A blueprint is a general-purpose model for describing systems, services, or any orchestrated object topology. Based on your selection, the wizard will automatically upload blueprints describing your requested system to the manager such that you will be able to generate instances of such deployments.


![2_getting_started_technologies.png]( /images/getting_started/2_getting_started_technologies.png )

If your selection requires secrets you'll be promoted to a step to set up secrets. If you selected more than one technology you might have a several steps to set up the secrets.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
If your selection requires secrets you'll be promoted to a step to set up secrets. If you selected more than one technology you might have a several steps to set up the secrets.
If your selection requires secrets, you'll be promoted to a secret set u step. If you selected more than one technology you might have several secret setup steps.


If your selection requires secrets you'll be promoted to a step to set up secrets. If you selected more than one technology you might have a several steps to set up the secrets.

To continue you'll need to feel all the required fields and continue by pressing the `Next` button.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
To continue you'll need to feel all the required fields and continue by pressing the `Next` button.
To continue you'll need to fill all the required fields and continue by pressing the `Next` button.


You can close the wizard and and proceed to create your first deployment.

## Disable Getting started Wizard
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
## Disable Getting started Wizard
## Disable the Getting Started wizard

The following secrets will be created. The value in parentheses is the secret name that will be created:

* AWS Access Key ID (aws_access_key_id)
* AWS Secret Access Key (aws_secret_access_key)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
* AWS Secret Access Key (aws_secret_access_key)
* AWS Secret Access Key (aws_secret_access_key)
AWS credentials can be created by following the guide [here](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_access-keys.html#Using_CreateAccessKey).

The following secrets will be created. The value in parentheses is the secret name that will be created:

* AWS Access Key ID (aws_access_key_id)
* AWS Secret Access Key (aws_secret_access_key)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
* AWS Secret Access Key (aws_secret_access_key)
* AWS Secret Access Key (aws_secret_access_key)
AWS credentials can be created by following the guide [here](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_access-keys.html#Using_CreateAccessKey).

* Azure Subscription ID (azure_subscription_id)
* Azure Tenant ID (azure_tenant_id)
* Azure Client ID (azure_client_id)
* Azure Client Secret (azure_client_secret)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
* Azure Client Secret (azure_client_secret)
* Azure Client Secret (azure_client_secret)
Azure credentials can be created by following the guide [here]({{< relref "/working_with/official_plugins/infrastructure/azure" >}}).

The following secrets will be created. The value in parentheses is the secret name that will be created:

* AWS Access Key ID (aws_access_key_id)
* AWS Secret Access Key (aws_secret_access_key)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
* AWS Secret Access Key (aws_secret_access_key)
* AWS Secret Access Key (aws_secret_access_key)
AWS credentials can be created by following the guide [here](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_access-keys.html#Using_CreateAccessKey).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants