184 results found
-
Add commit hash to application card in dashboard
It would be great if the commit hash was also included in the application card within the dashboard view. Currently, it only shows the branch that is deployed to, but it doesn't show which commit was last deployed. Why does this matter? I have two "application" cards in different environments (staging and production). I can't easily see whether staging and production are running on the same commit, or if production is behind. I know I can hover over the branch name to see the commit hash, but I have to do that twice to compare the hashes. Additionally, on some…
1 vote -
Provide 'Publish' Service cx Command
In the UI, there’s the ability to
Deploy with Options...
for an Application and you can select to onlyPublish
a service.It would be great to have a cx command to do the same thing instead of a full redeploy. One of the use cases we have is we're updating environment variables so we just need to Publish. It’s much faster and it wouldn't use the extra BuildGrid time.
This works with CSv1 but does not work with CSv2.
1 vote -
clean removal of all added AWS services when deleting a project
Hey,
I am using c66 now for quite some time and projects, and recently stumbled on this: when deleting a project, it removes the main EC2 instance on AWS, but leaves behind:
- volumes
- load balancers
- security groups
- key pairs
Not sure about the RDS instance, for that short-lived project, I opted to just have the db run on the one EC2 instance as well..
I would actually expect, that every additional service added for a project is cleaned up on AWS when deleting the project. At least a little warning would be nice, or a checkbox asking, if you want…
1 vote -
Always show the current stack without scrolling
With a lot of stacks, it is impossible to know what stack I'm currently looking at without repeatedly scrolling up to the header and the back down to what I was looking at. With multiple tabs open in order to try to copy settings, for instance, it makes it incredibly difficult to know what I'm looking at.
The name of the stack being viewed should always be visible in the top fixed header.
1 vote -
Add the option to importing specific backup from one stack to another in the UI
The import database feature can be used to test staging environment against production data. Having a way to specify the exact backup ID to import (rather than only having the very last one available) in the UI - with a dropdown or text field entry for the backup ID will be useful to cover more testing scenarios.
1 vote -
Partner with UpCloud
I want to deploy to UpCloud and not have to create registered servers.
1 vote -
Ubuntu 20.04
Allow deployment to Ubuntu 20.04
1 vote -
Read only users for Slave databases
As per the Ruby on Rails guide for a multi db setup;
the username for the writers and replicas should be different, and the replica user's permissions should be set to only read and not write.
1 vote -
Ability to set up firewall rules through manifest file
Add an option to automate firewall rules installation through manifest.yml file
e.g.
staging:
firewall_rules:
from: 127.0.0.1/16
to: 123.123.123.123
protocol: tcp
port: 221 vote -
Update the API docs
The API is very handy when you need to automate stuff but the documentation is not up to date. I would rather not have to bother the support with questions regarding missing things in the docs.
1 vote -
More groups in Rolling Deployment
Increasing the number of groups in a rolling deployment would be more feasible for certain deployments. It would also allow us to run better than half capacity.
1 vote -
Add AWS load balancer response codes to httpchk
This would save time so as not to have to go to the AWS UI to configure these separately. On the same note "Redirect HTTP to HTTPS" option should include an expected response option. Meaning if my server is expected to send anything other than a 200 response to the check, the server will return as healthy. For example, a 301 or 302.
1 vote -
Deploy previews based on pull request source branch
Currently you can only filter on the target branch, but it'd be nice to be able to filter on the source branch name within the PR config.
E.g. have a PR config with:
- source branch pattern (the new option I'm suggesting)
- target branch pattern (currently the only option)Then I could open a PR against the stack branch (e.g.
staging
), but only have it spin up a preview environment if my source branch is e.g.feature-123
and my source pattern isfeature*
.1 vote -
Deploy previews based on pull request labels
When configuring preview deployments based on pull requests, filter by label(s).
E.g. if a PR is opened (or labels are added or removed from an existing PR), if it contains certain labels, deploy a preview.
1 vote -
SSH identity federation (cx ssh) without the app deployment part
The "cx ssh" command is pretty useful for SSH identity management, since we manage in a central place who is able to login on each application stack. I also saw that command opens the SSH port on demand.
But for now, this "cx command" only applies to servers fully managed by Cloud66, which includes the application deployment part.
Feature request: Please allow the installation of the cx_agent on Ubuntu servers without the app deployment part, at a favourable price.
Thanks so much the Cloud66 team for your assistance.
1 vote -
JSON output for all cx commands
The Cloud66 API returns JSON for every endpoint, while cx primarily outputs formatted text. As a cx user, I would like to have optional JSON output instead of formatted text so I can use cx output more easily in scripts.
One approach I would like to offer is a --output=json flag for each command. Thank you!
1 vote -
log rotation with file size
Please add an option for Log rotation by file size.Like below example
/var/log/apache2/* {
weekly
rotate 3
size 10M
compress
delaycompress
}where size is specified 10M
1 voteThank you for your feedback. This request has been initially reviewed and is under consideration. Further updates will be provided as soon as there is substantial update.
-
VPC configuration through manifest when using Digital Ocean
At the moment all droplets created within Digital Ocean are placed onto the default VPC. This makes it difficult to provide network segregation if multiple stacks are deployed onto the same Digital Ocean cloud.
1 vote -
Improve CI/CD tooling support
The current solution for CI/CD integration (e.g. GitLab) is to use curl to hit a redeploy hook that sends a signal to Cloud66 for deploying the application. This doesn't integrate very well with pipeline flows, since there's no guarantee the deploy will succeed. Meanwhile the pipeline is marked as passed, but in reality the app failed to deploy.
The CX Toolbelt does offer an option to --listen, which is great. However, this Toolbelt is clearly intended for manual use and not by something like Docker or a CI pipeline script. This is possible but not officially supported, and the setup…
1 vote -
Add server tags as liquid template properties in HAProxy CustomConfig
I'd like to be able to create multiple backends in my HAProxy configuration based on the tags that are attached to servers. This would enable me to create path based routing so that I can have web servers solely dedicated to API requests.
1 vote
- Don't see your idea?