You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "DaanHoogland (via GitHub)" <gi...@apache.org> on 2025/11/18 10:36:44 UTC
[PR] add ‘external integrations' [cloudstack-www]
DaanHoogland opened a new pull request, #386:
URL: https://github.com/apache/cloudstack-www/pull/386
(no comment)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@cloudstack.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] add ‘external integrations' [cloudstack-www]
Posted by "Copilot (via GitHub)" <gi...@apache.org>.
Copilot commented on code in PR #386:
URL: https://github.com/apache/cloudstack-www/pull/386#discussion_r2537453926
##########
src/pages/security.md:
##########
@@ -23,6 +23,7 @@ In addition to that, it is your own responsibility, as an operator to
- protect against DoS and brute-force attacks.
- provide full fledged monitoring. Though some facilities are provided, putting appropriate monitoring remains the ultimate responsibility of the operator.
- ensure the security and integrity, including safeguarding them against unauthorized external access of critical cloud resources. These include, but are not limited to OS level access to Hosts, Management Servers, SystemVMs and routers.
+- make sure `external integrations` are save to use.
Review Comment:
Spelling error: "save" should be "safe".
```suggestion
- make sure `external integrations` are safe to use.
```
##########
src/pages/security.md:
##########
@@ -23,6 +23,7 @@ In addition to that, it is your own responsibility, as an operator to
- protect against DoS and brute-force attacks.
- provide full fledged monitoring. Though some facilities are provided, putting appropriate monitoring remains the ultimate responsibility of the operator.
- ensure the security and integrity, including safeguarding them against unauthorized external access of critical cloud resources. These include, but are not limited to OS level access to Hosts, Management Servers, SystemVMs and routers.
+- make sure `external integrations` are save to use.
Review Comment:
[nitpick] The backticks around `external integrations` are unnecessary here. This doesn't appear to be code or a technical term that requires code formatting. Consider removing them for consistency with the rest of the list items which don't use backticks for similar concepts.
```suggestion
- make sure external integrations are safe to use.
```
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@cloudstack.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] add ‘external integrations' [cloudstack-www]
Posted by "shwstppr (via GitHub)" <gi...@apache.org>.
shwstppr commented on code in PR #386:
URL: https://github.com/apache/cloudstack-www/pull/386#discussion_r2538309753
##########
src/pages/security.md:
##########
@@ -23,7 +23,7 @@ In addition to that, it is your own responsibility, as an operator to
- protect against DoS and brute-force attacks.
- provide full fledged monitoring. Though some facilities are provided, putting appropriate monitoring remains the ultimate responsibility of the operator.
- ensure the security and integrity, including safeguarding them against unauthorized external access of critical cloud resources. These include, but are not limited to OS level access to Hosts, Management Servers, SystemVMs and routers.
-- make sure `external integrations` are save to use.
+- make sure `external integrations` are safe to use.
Review Comment:
Should we specify that by external integration, it is referring to custom integations done via extensions feature and specifically executables or scripts added for custom extensions?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@cloudstack.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] add ‘external integrations' [cloudstack-www]
Posted by "DaanHoogland (via GitHub)" <gi...@apache.org>.
DaanHoogland merged PR #386:
URL: https://github.com/apache/cloudstack-www/pull/386
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@cloudstack.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] add ‘external integrations' [cloudstack-www]
Posted by "DaanHoogland (via GitHub)" <gi...@apache.org>.
DaanHoogland commented on code in PR #386:
URL: https://github.com/apache/cloudstack-www/pull/386#discussion_r2564356475
##########
src/pages/security.md:
##########
@@ -23,7 +23,7 @@ In addition to that, it is your own responsibility, as an operator to
- protect against DoS and brute-force attacks.
- provide full fledged monitoring. Though some facilities are provided, putting appropriate monitoring remains the ultimate responsibility of the operator.
- ensure the security and integrity, including safeguarding them against unauthorized external access of critical cloud resources. These include, but are not limited to OS level access to Hosts, Management Servers, SystemVMs and routers.
-- make sure `external integrations` are save to use.
+- make sure `external integrations` are safe to use.
Review Comment:
```suggestion
- make sure scripts and executables added as custom integrations in the extensions framework, are safe to use.
```
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@cloudstack.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org