Listen to this article. Also available on Spotify. Subscribe to PolyAPI Squawk.
With Release 19, we introduced optional contexts for environment objects and refactored environment names to be code-safe—restricting them to specific characters and eliminating spaces. While this update has no immediate practical application, it lays the foundation for exciting future capabilities.
In the future, we plan to leverage context-based environment referencing to enable:
- Cross-Environment API Keys and Permissions
- Generate API keys or grant permissions that span multiple environments by mapping them to a context path containing multiple environments.
- Automation and Environment Management
- Pass the contextNames as an argument to Poly functions to facilitate actions such as environment replication and promotion.
- This will enable automation across multiple environments, even across different tenants.
- Using contextNames is crucial when environments are dynamically created or deleted, ensuring a stable reference when IDs are not guaranteed to remain constant.
- Programmatic Environment Actions
- Develop environment functions to perform operations within code, such as programmatically enabling logging via environment-namespaced functions.
We believe that programmatic environment referencing through contextNames will be a vital capability for provisioning, managing, and operating PolyAPI.
Although these enhancements are not yet scheduled for release, they are an integral part of our short- to mid-term vision.
Want to try the new APIs?
Sign up for free and use your admin key to go to your Environments and you will see the context field if you edit or create an environment. Like I said above it’s not yet used, but will be in the near future.
Have questions about our roadmap or platform? We’d love to hear from you! Reach out to us at hello@polyapi.io,fill out a contact form or book an intro meeting.