Fill gaps from assistant conversations: CLI, deploy, associations - #724
Open
mintlify[bot] wants to merge 2 commits into
Open
mintlify[bot] wants to merge 2 commits into
mintlify[bot] wants to merge 2 commits into
Conversation
Contributor
Author
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
This file contains hidden or 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
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.
Summary
Targeted clarifications for recurring assistant questions about inspecting specific installations, how
amp deployaffects existing installations, and HubSpot association change events.Changes
cli/reference.mdx: note onlist:installationsexplaining how to fetch a single installation by ID or filter by customer (groupRef) via the API, since the CLI has no filter flags.cli/reference.mdx: note ondeployclarifying that deploying creates a new revision without changing existing installation configs, and thatenabled: alwaysobjects are the exception.manifest-reference.mdx: expanded theenabled: alwaysdescription to state it applies to existing installations immediately after deploy.provider-guides/hubspot.mdx: added a pointer from the Associations section toassociationChangeEventdocs in Subscribe Actions.Context
Assistant query buckets in the past week showed repeated questions about filtering installations by customer ID, whether deployed read-action changes auto-apply to installations, and which providers support association events.