{"owner":"bottlerocket-os","repo":"bottlerocket","hasSkills":true,"totalSkillsCount":1,"totalTokensCount":448,"categories":["plugin-manifest"],"hasMcp":false,"mcpConfig":null,"found":["tools/pubsys/policies/ssm/README.md"],"skills":{"tools/pubsys/policies/ssm/README.md":"# Parameter templates\n\nFiles in this directory contain template strings that are used to generate SSM parameter names and values.\nYou can pass a different directory to `pubsys` to use a different set of parameters.\n\nThe directory is expected to contain a file named `defaults.toml` with a table entry per parameter, like this:\n\n```toml\n[[parameter]]\nname = \"{variant}/{arch}/{image_version}/image_id\"\nvalue = \"{image_id}\"\n```\n\nThe `name` and `value` can contain template variables that will be replaced with information from the current build and from the AMI registered from that build.\n\nThe available variables include:\n* `variant`, for example \"aws-ecs-2\"\n* `arch`, for example \"x86_64\" or \"arm64\".\n  * Note: \"amd64\" and \"aarch64\" are mapped to \"x86_64\" and \"arm64\", respectively, to match the names used by EC2.\n* `image_id`, for example \"ami-0612c21373a768f20\"\n* `image_name`, for example \"bottlerocket-aws-ecs-2-x86_64-v1.42.0-5ed15786\"\n* `image_version`, for example \"1.42.0-5ed15786\"\n* `region`, for example \"us-west-2\"\n\n# Conditional parameters\n\nYou can also list parameters that only apply to specific variants or architectures.\nTo do so, add `variant` or `arch` keys (or both) to your parameter definition.\nThe parameter will only be populated if the current `variant` or `arch` matches one of the values in the list.\n(If both `variant` and `arch` are listed, the build must match an entry from both lists.)\n\nFor example, to add an extra parameter that's only set for \"aarch64\" builds of the \"aws-ecs-2\" variant:\n```toml\n[[parameter]]\narch = [\"aarch64\"]\nvariant = [\"aws-ecs-2\"]\nname = \"/a/special/aarch64/ecs/parameter\"\nvalue = \"{image_name}\"\n```\n"},"files":{"tools/pubsys/policies/ssm/README.md":"# Parameter templates\n\nFiles in this directory contain template strings that are used to generate SSM parameter names and values.\nYou can pass a different directory to `pubsys` to use a different set of parameters.\n\nThe directory is expected to contain a file named `defaults.toml` with a table entry per parameter, like this:\n\n```toml\n[[parameter]]\nname = \"{variant}/{arch}/{image_version}/image_id\"\nvalue = \"{image_id}\"\n```\n\nThe `name` and `value` can contain template variables that will be replaced with information from the current build and from the AMI registered from that build.\n\nThe available variables include:\n* `variant`, for example \"aws-ecs-2\"\n* `arch`, for example \"x86_64\" or \"arm64\".\n  * Note: \"amd64\" and \"aarch64\" are mapped to \"x86_64\" and \"arm64\", respectively, to match the names used by EC2.\n* `image_id`, for example \"ami-0612c21373a768f20\"\n* `image_name`, for example \"bottlerocket-aws-ecs-2-x86_64-v1.42.0-5ed15786\"\n* `image_version`, for example \"1.42.0-5ed15786\"\n* `region`, for example \"us-west-2\"\n\n# Conditional parameters\n\nYou can also list parameters that only apply to specific variants or architectures.\nTo do so, add `variant` or `arch` keys (or both) to your parameter definition.\nThe parameter will only be populated if the current `variant` or `arch` matches one of the values in the list.\n(If both `variant` and `arch` are listed, the build must match an entry from both lists.)\n\nFor example, to add an extra parameter that's only set for \"aarch64\" builds of the \"aws-ecs-2\" variant:\n```toml\n[[parameter]]\narch = [\"aarch64\"]\nvariant = [\"aws-ecs-2\"]\nname = \"/a/special/aarch64/ecs/parameter\"\nvalue = \"{image_name}\"\n```\n"},"items":[{"name":"README.md","path":"tools/pubsys/policies/ssm/README.md","rawUrl":"https://raw.githubusercontent.com/bottlerocket-os/bottlerocket/HEAD/tools/pubsys/policies/ssm/README.md","title":"ssm Documentation","category":"plugin-manifest","format":"markdown","content":"# Parameter templates\n\nFiles in this directory contain template strings that are used to generate SSM parameter names and values.\nYou can pass a different directory to `pubsys` to use a different set of parameters.\n\nThe directory is expected to contain a file named `defaults.toml` with a table entry per parameter, like this:\n\n```toml\n[[parameter]]\nname = \"{variant}/{arch}/{image_version}/image_id\"\nvalue = \"{image_id}\"\n```\n\nThe `name` and `value` can contain template variables that will be replaced with information from the current build and from the AMI registered from that build.\n\nThe available variables include:\n* `variant`, for example \"aws-ecs-2\"\n* `arch`, for example \"x86_64\" or \"arm64\".\n  * Note: \"amd64\" and \"aarch64\" are mapped to \"x86_64\" and \"arm64\", respectively, to match the names used by EC2.\n* `image_id`, for example \"ami-0612c21373a768f20\"\n* `image_name`, for example \"bottlerocket-aws-ecs-2-x86_64-v1.42.0-5ed15786\"\n* `image_version`, for example \"1.42.0-5ed15786\"\n* `region`, for example \"us-west-2\"\n\n# Conditional parameters\n\nYou can also list parameters that only apply to specific variants or architectures.\nTo do so, add `variant` or `arch` keys (or both) to your parameter definition.\nThe parameter will only be populated if the current `variant` or `arch` matches one of the values in the list.\n(If both `variant` and `arch` are listed, the build must match an entry from both lists.)\n\nFor example, to add an extra parameter that's only set for \"aarch64\" builds of the \"aws-ecs-2\" variant:\n```toml\n[[parameter]]\narch = [\"aarch64\"]\nvariant = [\"aws-ecs-2\"]\nname = \"/a/special/aarch64/ecs/parameter\"\nvalue = \"{image_name}\"\n```\n","isInternal":false,"tokens":448,"sizeBytes":1658}],"systemPromptSnippet":"<yakaai_skills repo=\"bottlerocket-os/bottlerocket\">\n<!-- File: tools/pubsys/policies/ssm/README.md (Tokens: ~448 | Category: plugin-manifest) -->\n# Parameter templates\n\nFiles in this directory contain template strings that are used to generate SSM parameter names and values.\nYou can pass a different directory to `pubsys` to use a different set of parameters.\n\nThe directory is expected to contain a file named `defaults.toml` with a table entry per parameter, like this:\n\n```toml\n[[parameter]]\nname = \"{variant}/{arch}/{image_version}/image_id\"\nvalue = \"{image_id}\"\n```\n\nThe `name` and `value` can contain template variables that will be replaced with information from the current build and from the AMI registered from that build.\n\nThe available variables include:\n* `variant`, for example \"aws-ecs-2\"\n* `arch`, for example \"x86_64\" or \"arm64\".\n  * Note: \"amd64\" and \"aarch64\" are mapped to \"x86_64\" and \"arm64\", respectively, to match the names used by EC2.\n* `image_id`, for example \"ami-0612c21373a768f20\"\n* `image_name`, for example \"bottlerocket-aws-ecs-2-x86_64-v1.42.0-5ed15786\"\n* `image_version`, for example \"1.42.0-5ed15786\"\n* `region`, for example \"us-west-2\"\n\n# Conditional parameters\n\nYou can also list parameters that only apply to specific variants or architectures.\nTo do so, add `variant` or `arch` keys (or both) to your parameter definition.\nThe parameter will only be populated if the current `variant` or `arch` matches one of the values in the list.\n(If both `variant` and `arch` are listed, the build must match an entry from both lists.)\n\nFor example, to add an extra parameter that's only set for \"aarch64\" builds of the \"aws-ecs-2\" variant:\n```toml\n[[parameter]]\narch = [\"aarch64\"]\nvariant = [\"aws-ecs-2\"]\nname = \"/a/special/aarch64/ecs/parameter\"\nvalue = \"{image_name}\"\n```\n</yakaai_skills>"}