Connect Bluemix IBM Containers and Bungie.Net
Describe what you want to happen between Bluemix IBM Containers and Bungie.Net in plain words. HumDay writes the program, proves it on real data, and runs it — no node graph, no field mapping, and no connector to wait for.
What HumDay can do on each side
Read from each provider’s own published API description, in their words.
Bluemix IBM Containers
47 documented operations. See all Bluemix IBM Containers operations
- POSTCreate a file share in a space
/volumes/fs/create - DELETEDelete a file share
/volumes/fs/{name} - POSTCreate a volume in a space
/volumes/create - POSTCreate and start a single container
/containers/create - POSTCreate and start a container group
/containers/groups - POSTShare a volume with another space
/volumes/{name}
Bungie.Net
134 documented operations. See all Bungie.Net operations
- POSTGiven the prefix of a global display name
/User/Search/GlobalName/{page}/ - POSTAdd a new optional conversation/chat channel
/GroupV2/{groupId}/OptionalConversations/Add/ - POSTEquip an item. You must have a valid Destiny Account
/Destiny2/Actions/Items/EquipItem/ - POSTEquip a list of items by itemInstanceIds
/Destiny2/Actions/Items/EquipItems/ - POSTSearch for Groups
/GroupV2/Search/ - POSTSet the Lock State for an instanced item
/Destiny2/Actions/Items/SetLockState/
How a Bluemix IBM Containers and Bungie.Net automation gets built
- Describe the outcome. Say what should happen — not which endpoints to call. HumDay works out which operations each side needs.
- Approve the contract. Before anything is built you see exactly what it will do in Bluemix IBM Containers and Bungie.Net, and what it will never do.
- See it proven. The program runs and shows you the result before it is allowed near either live account.
- Grant access, then go live. You approve the specific operations it may use on each side — and only those.
Related integrations
- Bluemix IBM Containers and OData for namespace microsoft.graphintegration
- Bungie.Net and OData for namespace microsoft.graphintegration
- Bluemix IBM Containers and Cloudflareintegration
- Bungie.Net and Cloudflareintegration
- Bluemix IBM Containers and NetBoxintegration
- Bungie.Net and NetBoxintegration
- Bluemix IBM Containers and GitHubintegration
- Bungie.Net and GitHubintegration
- Bluemix IBM Containers and Mistintegration
- Bungie.Net and Mistintegration
Questions about connecting Bluemix IBM Containers and Bungie.Net
- Can Bluemix IBM Containers connect with Bungie.Net?
- Yes. HumDay reads both providers' own published API descriptions and derives what each one can do, so neither side needs a hand-built connector before you can use it.
- How do I connect Bluemix IBM Containers to Bungie.Net?
- Describe the outcome you want in plain words. HumDay agrees a contract with you saying exactly what it will do, writes the program, and shows you a proof run before either account is touched.
- Do I need to write code to integrate Bluemix IBM Containers and Bungie.Net?
- No. There is no node graph to wire up and no field mapping to do. You say what should happen and HumDay works out which operations it needs from each side.
- What can HumDay do across Bluemix IBM Containers and Bungie.Net?
- Bluemix IBM Containers publishes 47 documented operations and Bungie.Net publishes 134. HumDay only ever uses the specific ones your approved contract needs.
- Is it safe to connect both accounts?
- Your credentials are stored encrypted and never appear in chat, code, or logs. Anything that writes to either Bluemix IBM Containers or Bungie.Net is held behind an approval you grant explicitly.
Where this came from
Operations are read from the published API descriptions for Bluemix IBM Containers and Bungie.Net. Descriptions are each provider’s own words, not ours.