Implement GraphQL endpoint to determine if an environment is halted or is on expert mode #8796
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
Bumps [sqlalchemy](https://github.com/sqlalchemy/sqlalchemy) from 2.0.37 to 2.0.38. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/sqlalchemy/sqlalchemy/releases">sqlalchemy's releases</a>.</em></p> <blockquote> <h1>2.0.38</h1> <p>Released: February 6, 2025</p> <h2>engine</h2> <ul> <li> <p><strong>[engine] [bug]</strong> Fixed event-related issue where invoking <code>Engine.execution_options()</code> on a <code>Engine</code> multiple times while making use of event-registering parameters such as <code>isolation_level</code> would lead to internal errors involving event registration.</p> <p>References: <a href="https://www.sqlalchemy.org/trac/ticket/12289">#12289</a></p> </li> </ul> <h2>sql</h2> <ul> <li> <p><strong>[sql] [bug]</strong> Reorganized the internals by which the <code>.c</code> collection on a <code>FromClause</code> gets generated so that it is resilient against the collection being accessed in concurrent fashion. An example is creating a <code>Alias</code> or <code>Subquery</code> and accessing it as a module level variable. This impacts the Oracle dialect which uses such module-level global alias objects but is of general use as well.</p> <p>References: <a href="https://www.sqlalchemy.org/trac/ticket/12302">#12302</a></p> </li> <li> <p><strong>[sql] [bug]</strong> Fixed SQL composition bug which impacted caching where using a <code>None</code> value inside of an <code>in_()</code> expression would bypass the usual "expanded bind parameter" logic used by the IN construct, which allows proper caching to take place.</p> <p>References: <a href="https://www.sqlalchemy.org/trac/ticket/12314">#12314</a></p> </li> </ul> <h2>postgresql</h2> <ul> <li> <p><strong>[postgresql] [usecase] [asyncio]</strong> Added an additional <code>asyncio.shield()</code> call within the connection terminate process of the asyncpg driver, to mitigate an issue where terminate would be prevented from completing under the anyio concurrency library.</p> <p>References: <a href="https://www.sqlalchemy.org/trac/ticket/12077">#12077</a></p> </li> <li> <p><strong>[postgresql] [bug]</strong> Adjusted the asyncpg connection wrapper so that the <code>connection.transaction()</code> call sent to asyncpg sends <code>None</code> for <code>isolation_level</code> if not otherwise set in the SQLAlchemy dialect/wrapper, thereby allowing asyncpg to make use of the server level setting for <code>isolation_level</code> in the absense of a client-level setting. Previously, this behavior of asyncpg was blocked by a hardcoded <code>read_committed</code>.</p> </li> </ul> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li>See full diff in <a href="https://github.com/sqlalchemy/sqlalchemy/commits">compare view</a></li> </ul> </details> <br /> [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details>
Bumps [logfire](https://github.com/pydantic/logfire) from 3.6.1 to 3.6.4. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/pydantic/logfire/releases">logfire's releases</a>.</em></p> <blockquote> <h2>v3.6.4</h2> <ul> <li>Handle mocks by calling <code>to_dict</code> on type by <a href="https://github.com/alexmojaki"><code>@alexmojaki</code></a> in <a href="https://redirect.github.com/pydantic/logfire/pull/897">#897</a></li> </ul> <h2>v3.6.3</h2> <ul> <li>Handle missing <code>shutdown</code> and <code>force_flush</code> on <code>NoOpLoggerProvider</code> better by <a href="https://github.com/alexmojaki"><code>@alexmojaki</code></a> in <a href="https://redirect.github.com/pydantic/logfire/pull/895">#895</a></li> <li>Handle missing events SDK by <a href="https://github.com/alexmojaki"><code>@alexmojaki</code></a> in <a href="https://redirect.github.com/pydantic/logfire/pull/893">#893</a></li> </ul> <h2>v3.6.2</h2> <ul> <li>Fix typing errors involving <code>handle_internal_errors</code> by <a href="https://github.com/alexmojaki"><code>@alexmojaki</code></a> in <a href="https://redirect.github.com/pydantic/logfire/pull/885">#885</a></li> <li>Avoid double shutdown of logger provider by <a href="https://github.com/alexmojaki"><code>@alexmojaki</code></a> in <a href="https://redirect.github.com/pydantic/logfire/pull/878">#878</a></li> </ul> </blockquote> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/pydantic/logfire/blob/main/CHANGELOG.md">logfire's changelog</a>.</em></p> <blockquote> <h2>[v3.6.4] (2025-02-25)</h2> <ul> <li>Handle mocks by calling <code>to_dict</code> on type by <a href="https://github.com/alexmojaki"><code>@alexmojaki</code></a> in <a href="https://redirect.github.com/pydantic/logfire/pull/897">#897</a></li> </ul> <h2>[v3.6.3] (2025-02-25)</h2> <ul> <li>Handle missing <code>shutdown</code> and <code>force_flush</code> on <code>NoOpLoggerProvider</code> better by <a href="https://github.com/alexmojaki"><code>@alexmojaki</code></a> in <a href="https://redirect.github.com/pydantic/logfire/pull/895">#895</a></li> <li>Handle missing events SDK by <a href="https://github.com/alexmojaki"><code>@alexmojaki</code></a> in <a href="https://redirect.github.com/pydantic/logfire/pull/893">#893</a></li> </ul> <h2>[v3.6.2] (2025-02-22)</h2> <ul> <li>Fix typing errors involving <code>handle_internal_errors</code> by <a href="https://github.com/alexmojaki"><code>@alexmojaki</code></a> in <a href="https://redirect.github.com/pydantic/logfire/pull/885">#885</a></li> <li>Avoid double shutdown of logger provider by <a href="https://github.com/alexmojaki"><code>@alexmojaki</code></a> in <a href="https://redirect.github.com/pydantic/logfire/pull/878">#878</a></li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/pydantic/logfire/commit/aa09b4b0da9b768d5885f5d98dcd0fd7c0225dbc"><code>aa09b4b</code></a> Release v3.6.4 (<a href="https://redirect.github.com/pydantic/logfire/issues/898">#898</a>)</li> <li><a href="https://github.com/pydantic/logfire/commit/18e2d5d48a6e63c24a548bd1a5941e6afb66deeb"><code>18e2d5d</code></a> Handle mocks by calling <code>to_dict</code> on type (<a href="https://redirect.github.com/pydantic/logfire/issues/897">#897</a>)</li> <li><a href="https://github.com/pydantic/logfire/commit/481a29072af19f960aeeeb9750496dc440add76e"><code>481a290</code></a> Release v3.6.3 (<a href="https://redirect.github.com/pydantic/logfire/issues/896">#896</a>)</li> <li><a href="https://github.com/pydantic/logfire/commit/e3b38addf3b05cf5aa8912270eedcb073901aa98"><code>e3b38ad</code></a> Handle missing events SDK (<a href="https://redirect.github.com/pydantic/logfire/issues/893">#893</a>)</li> <li><a href="https://github.com/pydantic/logfire/commit/12892c8cbb599b1bbe24367eb94d8c7a621df99f"><code>12892c8</code></a> Handle missing shutdown and force_flush on NoOpLoggerProvider better (<a href="https://redirect.github.com/pydantic/logfire/issues/895">#895</a>)</li> <li><a href="https://github.com/pydantic/logfire/commit/71cadbb5c967c367aa711fbdf8309cd5f69bea3c"><code>71cadbb</code></a> update slack link with 2k invite allowance (<a href="https://redirect.github.com/pydantic/logfire/issues/894">#894</a>)</li> <li><a href="https://github.com/pydantic/logfire/commit/1cf7db831ffbc6301fe5e96a1647c3810d4cf667"><code>1cf7db8</code></a> add note about supporting traces, metrics and logs (<a href="https://redirect.github.com/pydantic/logfire/issues/890">#890</a>)</li> <li><a href="https://github.com/pydantic/logfire/commit/e5f88d83830fee8847bc3a4a0b74c87e55f095c8"><code>e5f88d8</code></a> doc: document logs endpoint (<a href="https://redirect.github.com/pydantic/logfire/issues/889">#889</a>)</li> <li><a href="https://github.com/pydantic/logfire/commit/887ef08e3840412f0dd64874230977738086bb82"><code>887ef08</code></a> Fix OTel collector exporter endpoint (<a href="https://redirect.github.com/pydantic/logfire/issues/888">#888</a>)</li> <li><a href="https://github.com/pydantic/logfire/commit/cd2a66eb17cc2f6f5f6c695509d281c33022da3c"><code>cd2a66e</code></a> Release v3.6.2 (<a href="https://redirect.github.com/pydantic/logfire/issues/887">#887</a>)</li> <li>Additional commits viewable in <a href="https://github.com/pydantic/logfire/compare/v3.6.1...v3.6.4">compare view</a></li> </ul> </details> <br /> [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details>
…1.0 (PR #8790) Bumps inmanta-dev-dependencies[async,core,pytest] from 2.150.0 to 2.151.0. [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details>
…etermine-if-an-environment-is-on-expert-mode-or-halted
…n-environment-is-on-expert-mode-or-halted' of github.com:inmanta/inmanta-core into issue/8736-implement-graphql-endpoint-to-determine-if-an-environment-is-on-expert-mode-or-halted
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.
Description
closes Add ticket reference here
Self Check:
Strike through any lines that are not applicable (
~~line~~) then check the box