CodeNOW Roadmap & Features

1

CLI access to K8s clusters (kubectl)

This new feature empowers you to interact directly with Kubernetes clusters using kubectl, the same command-line tool you know and love. What sets this apart is how it integrates with CodeNOW's RBAC. The roles and permissions you define within our platform will now directly influence your access and capabilities in the Kubernetes environment. This seamless integration promises a more intuitive, efficient, and secure way to manage your clusters.

0

2

CodeNow API

Delivered

In today's fast-paced world, software development is all about speed, scalability, and staying ahead of the competition. CodeNow has been at the forefront of enabling development teams to achieve just that. With our robust and versatile API, we're taking a giant leap forward in empowering developers to build, scale, and automate like never before.

0

1

Ownership of applications

Open

Codenow will provide the option to set up the team as an owner of a single application. If anybody were interested in integrating with any service from this application, finding the owner would be much easier.

0

1

Move application component between applications

Open

Codenow will enable the movement of application components between applications and transfer all metadata about the application component under the target application.

0

1

Merge/Pull request as a trigger for CI pipelines

Open

Codenow will provide the capability to set up triggers for CI pipelines based on creating merge/pull requests in the Git repository.

0

1

Redesign deployment configuration

Delivered

Codenow will provide the capability of a 2-way or 3-way merge between default, previous, or newly created configurations for deployment to the target environment. The second enhancement for deployment configuration will be that user can mark any file in his repository as a configuration file, and the Codenow will provide the capability to change the file for any single environment. Then the Codenow will inject all configuration files to their respective locations in the runtime container corresponding to their location in the Git repository.

0

4

Use CRON for triggering CI pipelines

Future consideration

CodeNow will extend definitions of triggers CI pipelines by the option to trigger pipelines with CRON definition. The user would use this option, for example, for nightly builds and deployments.

0

2

Support for mono repositories

Planned for future release

CodeNow will provide the option to create a new application component like a part of the mono repository (git repository that hosted multiple application components). The user will use the feature to create a new component as a link from the existing Git repository and the repository would be a mono repository as well.

0

1

Create a new component in Github connected account

Planned for future release

Extend options for creating a new application component about choose GitHub as a target for your Git repository that would be created with the application component.

0

1

Redesign the creation of a new application component

Planned for future release

The number of options for creating new application components in CodeNow leads to a chaotic form. We decided to redesign the way to create the application component and introduce a new step-by-step wizard that provides a full spectrum of possibilities for how to create components in a more precise way.

0