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

ENDOC-438 Refine the config profiles, add doc on the config map, exte… #462

Merged
merged 2 commits into from
Mar 28, 2022

Conversation

nshaw
Copy link
Member

@nshaw nshaw commented Mar 28, 2022

…nd the CLI reference a bit

@nshaw nshaw requested review from jyunmitch and Lyd1aCla1r3 March 28, 2022 15:13
ent prj get-bundle-id --auto
```

If you have a microservice plugin in your project, an unique identifier will be calculated for it as well.
Copy link
Contributor

Choose a reason for hiding this comment

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

"a unique" (i looked it up to doublecheck :P)

@@ -64,24 +76,23 @@ data:
```

### Method 3: Default Profile
1. Create the parameter profile in the `OperatorConfigMap` in the data profile file at `data/entando.profile.[your-profile]`.
1. Create the parameter profile in the `OperatorConfigMap` in the data profile file at `data/entando.profile.[your-profile]`.
Copy link
Contributor

Choose a reason for hiding this comment

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

can omit "file" (reads awkwardly and no "file" follows "profile" above)

```

2. Add a reference to the profile at data/entando.plugins.defaultProfile:
2. Add a reference to the profile at data/entando.plugins.defaultProfile:
Copy link
Contributor

Choose a reason for hiding this comment

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

backticks on path (used above)

See [this tutorial](../../tutorials/create/ms/run-local.md) for more details.

### Get the Bundle ID and Plugin ID
Entando will use a unique identifier for your bundle as a way to provide additional security controls around bundle-specific resources. You can determine this identifier with this command
Copy link
Contributor

Choose a reason for hiding this comment

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

will use -> uses (present tense convention)


## Prerequisites
The Entando Operator makes use of an optional ```ConfigMap``` named ```entando-operator-config```. It must be present in the same namespace. In a quickstart environment you can check for its presence with this command:
```sh
Copy link
Contributor

Choose a reason for hiding this comment

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

i think there should be a comma after "environment"... @jyunmitch?

kubectl apply -f entando-operator-config.yaml -n entando
```

The Entando Operator will automatically reload the settings from the new ```ConfigMap```. You can verify the reload by checking the logs in the operator pod.
Copy link
Contributor

Choose a reason for hiding this comment

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

"automatically reloads" (present tense)

kubectl edit configmap/entando-operator-config -n entando
```

The Entando Operator will automatically reload the settings from the ```ConfigMap```. You can verify the reload by checking the logs in the operator pod. Some settings may only take effect when a deployment is first created, for example, timeout settings or cpu limits.
Copy link
Contributor

Choose a reason for hiding this comment

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

automatically reloads

"...created, for example, timeout..." -> "...created, e.g. timeout..." (to avoid use of the comma to introduce the example verbiage)


### Retrieve the Plugin ID
First you will need to retrieve the Plugin ID which is calculated during installation and written to the EntandoPlugin Custom Resource as part of the deployment of the plugin micro-service. Use the following command:
First you will need to [retrieve the Plugin ID](../../docs/reference/entando-cli.md) which is calculated during installation and written to the EntandoPlugin Custom Resource as part of the deployment of the plugin microservice. Use the following command from the project directory
Copy link
Contributor

Choose a reason for hiding this comment

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

comma after "First"

you will need -> you need

comma after "Plugin ID"

@nshaw nshaw merged commit 1353589 into ENDOC-438 Mar 28, 2022
@nshaw nshaw deleted the ENDOC-438-pt2 branch March 28, 2022 19:00
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