feat: add Studio Projects for 43 existing Integration Models - #101
Merged
Merged
Conversation
14 workflows across 5 folders (buckets, objects, bucket policy, versioning, tagging), covering the common-CRUD subset. Built locally, one atomic workflow per operation, not yet imported/tested against a live platform instance.
… Studio Projects - Amazon EKS: 25 workflows across 6 folders (clusters, addons, fargate profiles, nodegroups, identity provider configs, tags) - AWS Lambda: 30 workflows across 6 folders (functions incl. invoke, aliases, event source mappings, function URL configs, layers, tags) - AWS Network Firewall: 23 workflows across 5 folders (firewalls, firewall policies, rule groups, TLS inspection configurations, tags) - AWS Organizations: 25 workflows across 5 folders (organization, accounts, organizational units, policies, tags) - Amazon Route 53: 17 workflows across 5 folders (hosted zones, resource record sets, health checks, VPC associations, tags) Built locally, one atomic workflow per operation, not yet imported/tested against a live platform instance.
…dio Projects - Docker Engine: 21 workflows across 4 folders (containers, images, networks, volumes) - Docker Hub: 13 workflows across 4 folders (access tokens, repository tags, images, org settings) - GoDaddy Domains: 15 workflows across 4 folders (domain lifecycle, DNS records, availability/discovery, domain privacy) - OpenAI: 22 workflows across 5 folders (models, chat completions, files, fine-tuning jobs, assistants) - RingCentral: 22 workflows across 5 folders (calls, messages, extensions, meetings, presence) Built locally, one atomic workflow per operation, not yet imported/tested against a live platform instance.
…o Projects - Datadog: 24 workflows across 5 folders (incidents, downtimes, maintenance windows, roles, users) - LogicMonitor: 23 workflows across 5 folders (devices, device groups, websites, collectors, alerts) - New Relic: 22 workflows across 7 folders (applications, deployments, alert policies/conditions, incidents, key transactions) - PagerDuty: 29 workflows across 6 folders (incidents, services, escalation policies, schedules, users, teams) - Paessler PRTG: 24 workflows across 5 folders (devices, groups, probes, sensors, channels) Built locally, one atomic workflow per operation, not yet imported/tested against a live platform instance.
…e Drive, Kubernetes Studio Projects - Ansible AWX (Tower): 30 workflows across 6 folders (job templates, jobs, inventories, projects, credentials, hosts) - Apache Airflow: 26 workflows across 6 folders (DAGs, DAG runs, task instances, connections, pools, variables) - Google Cloud Compute Engine: 27 workflows across 5 folders (instances, disks, networks, firewalls, images) - Google Drive: 21 workflows across 4 folders (files, drives, permissions, comments) - Kubernetes: 30 workflows across 6 folders (pods, deployments, services, namespaces, configmaps, secrets) Built locally, one atomic workflow per operation, not yet imported/tested against a live platform instance.
…tudio Projects - 6connect Provision: 23 workflows across 5 folders (resources, attributes, links, attachments, actions) - Infoblox Threat Defense (BloxOne): 25 workflows across 5 folders (security policies, named lists, network lists, application filters, category filters) - Infoblox Universal DDI (BloxOne): 30 workflows across 6 folders (IPAM: IP spaces, address blocks, subnets, ranges, addresses; DHCP fixed addresses) - Nautobot: 25 workflows across 5 folders (devices, locations, IP addresses, prefixes, VLANs) Built locally, one atomic workflow per operation, not yet imported/tested against a live platform instance.
…Connect Studio Projects - Amazon API Gateway: 24 workflows across 5 folders (REST APIs, resources, methods, deployments, stages) - AWS CloudFormation: 19 workflows across 4 folders (stacks, change sets, stacksets, stack instances) - Amazon Cognito User Pools: 30 workflows across 6 folders (user pools, app clients, users, groups, identity providers, resource servers) - Amazon Connect: 25 workflows across 6 folders (instances, users, queues, routing profiles, contact flows, contact lifecycle) - AWS Direct Connect: 25 workflows across 7 folders (connections, virtual interfaces, DX gateways, gateway associations, LAGs, interconnects, BGP peers) Built locally, one atomic workflow per operation, not yet imported/tested against a live platform instance.
…ira Server & DC, Opsgenie Studio Projects - Bitbucket Cloud: 24 workflows across 5 folders (repositories, pull requests, commits, branches, projects) - Confluence Cloud: 20 workflows across 5 folders (pages, blog posts, spaces, attachments, comments) - Confluence Server & Data Center: 22 workflows across 5 folders (content, spaces, attachments, content labels, content properties) - Jira Server & Data Center: 29 workflows across 6 folders (issues, comments, projects, worklogs, components, versions) - Opsgenie: 26 workflows across 5 folders (alerts, teams, users, schedules, incidents) Built locally, one atomic workflow per operation, not yet imported/tested against a live platform instance.
…M Studio Projects - Cisco Crosswork Network Controller: 5 workflows across 2 folders (device inventory, L3VPN service intent CRUD) - Cisco ISE: 25 workflows across 5 folders (network devices, device groups, endpoints, policy sets, TrustSec virtual networks) - Cisco Webex: 30 workflows across 6 folders (memberships, messages, people, rooms, teams, team memberships) - Okta Management: 29 workflows across 6 folders (entitlements, entitlement bundles, collections, grants, labels, access certification campaigns) - Palo Alto Prisma Cloud CSPM: 16 workflows across 5 folders (alert lifecycle, AWS/Azure/GCP cloud account management) Built locally, one atomic workflow per operation, not yet imported/tested against a live platform instance.
- Selector AI Metastore Inventory: 15 workflows across 3 folders (inventory names, items, schema) - Selector AI Query: 1 workflow (S2QL query) - Slack Web API: 30 workflows across 6 folders (messaging, conversations, users, files, reactions, pins) - Sonatype Nexus Repository: 18 workflows across 5 folders (repositories, components, assets, search, status) - Twilio: 25 workflows across 5 folders (messages, calls, incoming phone numbers, conferences/participants, recordings) - Zoom: 24 workflows across 4 folders (meetings, users, webinars, cloud recording) Built locally, one atomic workflow per operation, not yet imported/tested against a live platform instance.
…he name itself) Both Selector build scripts had ADAPTER set to the title with a stray ' latest' suffix already baked in, so locationType came out as 'Selector AI — Query latest:latest' instead of 'Selector AI — Query:latest' — wouldn't have resolved against the real Integration Model. Caught by cross-checking every generated project's locationType against every -latest.json spec's actual info.title in the repo.
Ansible is the vendor/brand; AWX (Tower) is the actual product name, same relationship as NetScaler/ADC or Cisco/IOS. This predates the Studio Project work in this branch (structure was flat since 2026-07-10) but should be fixed before merging rather than building further on top of it. Moved OpenAPIs/, Studio Projects/, and README.md under a new 'AWX (Tower)/' product folder; no content changes.
Tower was renamed to Ansible Automation Platform (AAP) by Red Hat; AWX itself was never renamed and remains the correct name for the open-source upstream project this spec documents (confirmed via the product README, which already described AWX as 'the upstream open-source project behind Red Hat Ansible Automation Platform's Controller' — only the '(Tower)' qualifier was stale). No spec content changes, only naming: folder, filenames, info.title, and Studio Project adapter references.
Provision is 6connect's actual product name (matches its title in the existing spec, '6connect Provision'), same as HashiCorp/Vault or NetScaler/ADC. Keeps this PR consistent with the separate fix/vendor-product-directory-structure PR fixing this same issue repo-wide.
This branch was successfully deployed
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
2 participants
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.
Adds a companion Studio Project (common-CRUD-subset workflows) to every existing Integration Model that was missing one — closing the gap found in a full repo audit. One atomic workflow per operation, following this repo's existing conventions (task_start -> adapter task -> task_end, incoming params from required path/query params + requestBody, folder-per-resource-category).
Products covered (43)
AWS: API Gateway, CloudFormation, Cognito, Connect, Direct Connect, EKS, Lambda, Network Firewall, Organizations, Route 53, S3
Atlassian: Bitbucket Cloud, Confluence Cloud, Confluence Server & Data Center, Jira Server & Data Center, Opsgenie
Cisco: Crosswork Network Controller, ISE, Webex
Cloud/DevOps: Ansible (AWX/Tower), Apache Airflow, Google Cloud Compute Engine, Google Drive, Kubernetes
Security/Identity: Okta, Palo Alto Prisma Cloud CSPM
Observability/ITSM: Datadog, LogicMonitor, New Relic, PagerDuty, Paessler PRTG
Other SaaS: Docker Engine, Docker Hub, GoDaddy, OpenAI, RingCentral, Selector (2 projects), Slack, Sonatype Nexus, Twilio, Zoom, 6connect
DDI/DCIM: Infoblox Threat Defense (BloxOne), Infoblox Universal DDI (BloxOne), Nautobot
Notes
locationType/appvalues were cross-checked against each product's actual-latest.jsoninfo.titleand validated structurally (hex task IDs, complete transitions, adapter_id present) across all 1,048 generated workflows.