[Feature] [Platform] Do not require LM during install commands #1989
Conversation
There was a problem hiding this comment.
Copilot reviewed 7 out of 7 changed files in this pull request and generated 2 comments.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| kubectl create secret generic arango-license-key --from-literal=token-v2="<license-string>" | ||
|
|
||
| # For the License Manager Key | ||
| kubectl create secret generic arango-license-key --from-literal=license-client-id="<license-client-id>" --from-literal=license-client-secret="<license-client-secret>" |
There was a problem hiding this comment.
The examples for both license key types use the same secret name arango-license-key. This will cause a conflict if users try to create both secrets. Consider using different secret names (e.g., arango-license-key and arango-license-manager-key) or clarifying that only one should be used at a time.
| kubectl create secret generic arango-license-key --from-literal=license-client-id="<license-client-id>" --from-literal=license-client-secret="<license-client-secret>" | |
| kubectl create secret generic arango-license-manager-key --from-literal=license-client-id="<license-client-id>" --from-literal=license-client-secret="<license-client-secret>" |
| # For the License Key | ||
| kubectl create secret generic arango-license-key --from-literal=token-v2="<license-string>" | ||
|
|
||
| # For the License Manager Key | ||
| kubectl create secret generic arango-license-key --from-literal=license-client-id="<license-client-id>" --from-literal=license-client-secret="<license-client-secret>" |
There was a problem hiding this comment.
The examples for both license key types use the same secret name arango-license-key. This will cause a conflict if users try to create both secrets. Consider using different secret names (e.g., arango-license-key and arango-license-manager-key) or clarifying that only one should be used at a time.
No description provided.