We are using font-awesome V4 and should migrate to font-awesome V5 which comes with its own vue.js module: https://github.com/FortAwesome/vue-fontawesome

Migration includes removing old font-awesome V4 module and changing all existing icons to new vue.js tag.

This is blocked until #114 is merged which comes with first initial integration.

Good summary at https://matthewdf10.medium.com/how-to-enable-logging-on-every-aws-service-in-existence-circa-2021-5b9105b87c9 and https://docs.google.com/spreadsheets/d/1DBmCXX1irJvxdewa85p5nSsYEf3tpSKWBbwp700mbzs/edit#gid=0

Amazon Aurora
https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-rds-dbcluster.html#cfn-rds-dbcluster-enablecloudwatchlogsexports

AWS AppSync

Requirements

Add an environment parameter in the config.
This environment field should be added to all users in the param so we can add rules based on the environment and have the same config file for all your environment.

Hi,

It'd love to try out alloy_ci . We run almost everything in kubernetes (incl. gitlab runner) and I think it would be awesome if there was a template / manifests to deploy alloy on kubernetes.
This would make trying it out for evaluation purposes much easier.
Have no strong opinions on how a k8s example templates should be packaged but these are some options that come to my mind:

• simpl

Look into and create a POC of a public github action using rok8s-scripts

Bug report

Expected behaviour?
All projects should be included or excluded without any delay.

Actual behaviour?
All projects are included or excluded with a noticeable delay.

Steps to reproduce?

1. Add a feed with lots of projects (mine has ~140 projects)
2. Click the "exclude all" button

This is because it loops through all projects and triggers an include/exclude

fledge beta
Git error. Command: git log origin/dev..dev
fatal: ambiguous argument 'origin/dev..dev': unknown revision or path not in the working tree.
Use '--' to separate paths from revisions, like this:
'git [...] -- [...]'

Please suggest something to fix this...

In #26 we have discussed how a monospace comment could look like. Here is a suggestion:

508 tests   (+1)
482 success (+1)
 26 skipped (±0)
  0 failed  (±0)

Look at creating a custom GitHub Action for config-lint.

Resources:
https://github.com/actions/toolkit
https://help.github.com/en/actions/building-actions/creating-a-docker-container-action

As a pipeline status moves from initializing to running to completed or failed etc., the timestamp of the change should be recorded so that we can fetch them from the /metrics endpoint

When creating a new SHAFT_Engine maven project, the Properties folder is generated under the src/test/resources folder.

Steps To Reproduce:

1. Create a new SHAFT_Engine maven project
2. Check the src/test/resources folder
3. We can see that the Properties folder is generated in the above path

Expected behavior: The Properties folder should be generated under src/main/resources fol