Skip to content

Conversation

@Simran-B
Copy link
Contributor

@Simran-B Simran-B commented Jan 12, 2024

Description

type: object leads to only Response Body be rendered (after the response description). This is okay IMO, but it would be nicer if we could properly document endpoints like these using patternProperties and then a structured description of the sub-objects currently explained in free-text

No curl examples added because of potentially sensitive information in the reply / extremely long output.

Preview: https://deploy-preview-425--docs-hugo.netlify.app/devel/develop/http-api/administration/#get-the-startup-option-configuration

Upstream PRs

  • 3.10:
  • 3.11:
  • 3.12:

@arangodb-docs-automation
Copy link
Contributor

Deploy Preview Available Via
https://deploy-preview-425--docs-hugo.netlify.app

@cla-bot cla-bot bot added the cla-signed label Jan 12, 2024
@Simran-B Simran-B self-assigned this Jan 12, 2024
@Simran-B Simran-B added this to the 3.12 milestone Jan 12, 2024
Comment on lines 337 to 342
Alternatively, you can connect to an `arangod` instance with an
[ArangoShell](../../components/tools/arangodb-shell/_index.md) and invoke a
[JavaScript Transaction](../../develop/transactions/javascript-transactions.md)
by calling `db._executeTransaction()` with the following function to retrieve the
server options, but this is limited to Coordinators and single servers with
JavaScript/V8 enabled:
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 we should stop recommending the JavaScript variant, as now a proper alternative is available.

Copy link
Contributor Author

@Simran-B Simran-B Jan 12, 2024

Choose a reason for hiding this comment

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

My thought was that people may look at the eventually stable 3.12 documentation and try to use the HTTP API but it's not available in 3.11 and older, and keeping the old variant allows me to reference it in the release notes - I generally avoid linking between versions. But I think we can go with your suggestion

Copy link
Contributor

@jsteemann jsteemann left a comment

Choose a reason for hiding this comment

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

LGTM

@nerpaula nerpaula merged commit 681ad95 into main Jan 15, 2024
@nerpaula nerpaula deleted the options-api branch January 15, 2024 07:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants