website/load-docs.sh: add versioned docs for latest version #4222
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
With this change, we should get both a /docs/v0.36.1 and a /docs/latest in our deployed docs. Before, the symlink would have made hugo only build a /docs/latest, but not the other link. Signed-off-by: Stephan Renatus <stephan.renatus@gmail.com>
srenatus
force-pushed
the
sr/docs/keep-latest-and-latest-version
branch
from
e72a18b
to
bcbe7f6
Compare
anderseknert
approved these changes
Jan 13, 2022
damienjburks
pushed a commit
to damienjburks/opa
that referenced
this pull request
Jan 19, 2022
…icy-agent#4222) With this change, we should get both a /docs/v0.36.1 and a /docs/latest in our deployed docs. Before, the symlink would have made hugo only build a /docs/latest, but not the other link. Signed-off-by: Stephan Renatus <stephan.renatus@gmail.com> Signed-off-by: Damien Burks <damien@hackintosh.attlocal.net>
damienjburks
pushed a commit
to damienjburks/opa
that referenced
this pull request
Jan 19, 2022
Signed-off-by: Damien Burks <damien@hackintosh.attlocal.net> website/load-docs.sh: add versioned docs for latest version (open-policy-agent#4222) With this change, we should get both a /docs/v0.36.1 and a /docs/latest in our deployed docs. Before, the symlink would have made hugo only build a /docs/latest, but not the other link. Signed-off-by: Stephan Renatus <stephan.renatus@gmail.com> removing -l flag from the test subcommand Adding additional space to sign off on commit after removing -l from test.go Signed-off-by: Damien Burks <damien@hackintosh.attlocal.net> removing space Signed-off-by: Damien Burks <damien@hackintosh.attlocal.net> Add Dapr integration (open-policy-agent#4229) Also included some improvements to the Rego checks: * Pass GITHUB_TOKEN to policy to not exceed API quota * Ensure required attributes included in integration * Ensure commited .json files are valid JSON Signed-off-by: Anders Eknert <anders@eknert.com> Follow redirects in http.send Rego checks (open-policy-agent#4232) Signed-off-by: Anders Eknert <anders@eknert.com> fixing broken links in the online documentation (open-policy-agent#4224) Signed-off-by: Peter Helewski <phelewski@gmail.com> plugins/bundle: Update persisted bundle activation mechanism Earlier errors encountered during loading and activating persisted bundles would cause the OPA runtime to exit. This behavior is different from when OPA downloads a bundle and activation errors if any would possibly get resolved in successive download attempts. This fix adds a retry mechanism to activate persisted bundles in an attempt to mimic the behavior seen during bundle downloads. Errors if any encountered during the process will be surfaced in the bundle's status update and not result in an abrupt exit. Fixes: open-policy-agent#3840 Signed-off-by: Ashutosh Narkar <anarkar4387@gmail.com> built-ins: add graph.reachable_paths (open-policy-agent#4205) This new built-in functionality allows callers to find all reachable paths in a graph based on an array or set of root nodes. See the updates to policy-reference.md for more details and usage information. Signed-off-by: Justin Lindh <justin.lindh@webfilings.com> ast/parser: don't error when future kw import is redundant (open-policy-agent#4237) When passing `ParserOptions{AllFutureKeywords: true}` or `ParserOptions{FutureKeywords: []string{"in"}}` to the `ast` package's parse methods, and when parsing a module that contains import future.keywords.in then we would previously have raised an error: when the parser encountered the `in`, it complains about not expecting an "in" token there. Now, parsing imports is done with a scanner copy that knows nothing about the future keywords. Signed-off-by: Stephan Renatus <stephan.renatus@gmail.com> ast: Adding duplicate imports check to compiler strict mode (open-policy-agent#4228) When strict mode is enabled, an import shadowing another import is an error. Fixes: open-policy-agent#2698 Signed-off-by: Johan Fylling <johan.dev@fylling.se> ast: add `every` future keyword (parser, internal representation) (open-policy-agent#4179) * ast: add 'every' future keyword, parser support, scaffolding With this commit, "every x in xs { ... }" and "every k, v in { ... }" will be parsed into a new struct, which is basically Every { Key, Value *Term Domain *Term Body Body } This includes the required to changes to visitors, comparisons, copy, ... all the ceremony required to introduce a new keyword. * format: format every statements * ast: hide 'every' from capabilities for now With this change, - capabilities.json will NOT mention "every" - "import future.keywords" will NOT get you "every" - "import future.keywords.every" will complain about "every" being unknown In tests, we're passing an unexported field in `ast.ParserOptions`, which makes the parser treat "every" like it would eventually be treated when unveiled. The formatting tests are bluntly SKIPPED for now, to be re-enabled later. --------------- NB: The work on "every" is ongoing. Rewriting and evaluation follows. When it's documented, we'll unhide it. --------------- Signed-off-by: Stephan Renatus <stephan.renatus@gmail.com> bundle: Roundtrip manifest before hashing When OPA verifies the content of the manifest file, it first parses it into a JSON structure and then recursively orders the fields of all objects alphabetically and then applies the hash function. The same process was not followed while generating the hash for the manifest content which would result in a digest mismatch during verification. This can be observed with a manifest that contains metadata. Fixes: open-policy-agent#4233 Signed-off-by: Ashutosh Narkar <anarkar4387@gmail.com> Removing more deprecated code related to failureLine Signed-off-by: Damien Burks <damien@hackintosh.attlocal.net>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
With this change, we should get both a /docs/v0.36.1 and a /docs/latest
in our deployed docs.
Before, the symlink would have made hugo only build a /docs/latest,
but not the other link.