Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[FEATURE REQUEST] Add Provider Attribute to show support for SSL/TLS Wildcard Certs #201

Open
ourlink opened this issue May 16, 2024 · 1 comment
Labels
enhancement New feature or request P3 priority 3 feature/ enhancement

Comments

@ourlink
Copy link

ourlink commented May 16, 2024

In the list of Provider Attributes, offered through Cloudmos, currently, there does not exist any attribute to show that a Provider has deployed a WildCard SSL/TLS Certificate via LetsEncrypt. However, any provider can add SSL/TLS Certificates following the TLS Certs for Akash Provider (Optional Step) in the Akash Network Docs. ( https://akash.network/docs/providers/build-a-cloud-provider/tls-certs-for-akash-provider/ )

This feature request is for the Cloudmos team to add a set of attributes to display on the Provider Overview page highlighting the offering of SSL/TLS with any web deployment.

The request is to display SSL/TLS Offered=Y similar to how the attributes for Persistent Storage, IP Leases, and Custom Domain are displayed.

@baktun14
Copy link
Collaborator

baktun14 commented Jun 3, 2024

We can add a field in the Provider attribute form that makes it easy for provider to edit, but otherwise this is out of our control since it's up to the providers to set this attribute. Please create an issue under the support repo.

Related to (#194)

@baktun14 baktun14 added enhancement New feature or request P3 priority 3 feature/ enhancement labels Jun 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request P3 priority 3 feature/ enhancement
Projects
Status: Backlog (not prioritized)
Development

No branches or pull requests

2 participants