DOC-774 | New license management using credentials to activate deployments or generate license keys #843
+886
−228
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.
Description
Open tasks and questions:
-e ARANGO_LICENSE_KEYunless for e.g. air-gapped environments and link to the license management page for how to activate a deployment using the Platform CLI tool?Upstream PRs
Note
Documents new deployment ID endpoint, overhauls Enterprise license management (credentials-based activation/key generation), updates references/release notes, and adds a Data Platform installation guide with streamlined platform docs.
GET /_admin/deployment/idendpoint docs with OpenAPI, examples, and permissions.@arangodb/db-objectreferences to “Apply a license key”.installation.md(on-prem setup via Kubernetes, Operator, CLI, license secret, package install)._index.md(deployment options, aliases) and trimget-started.mdto a stub; adjust release notes links/wording.Written by Cursor Bugbot for commit 8b6fb74. This will update automatically on new commits. Configure here.