Skip to content

Conversation

@Aditya1404Sal
Copy link

  • Also adding a component that exports that provider (though I haven't pushed it to a registry).
  • it's currently working thru the [overrides] that point to the local wit artifact.

Feature or Problem

Related Issues

Release Information

Consumer Impact

Testing

Unit Test(s)

Acceptance or Integration

Manual Verification

wash build works (Created both the provider archive and the wasm component binaries) made sure that the Cargo.toml and wasmcloud.toml are in working condition.

…with it's respective component

Signed-off-by: Aditya <aditya.salunkh919@gmail.com>
@Aditya1404Sal Aditya1404Sal requested review from a team as code owners August 24, 2025 18:56
Signed-off-by: Aditya <aditya.salunkh919@gmail.com>
@JohnFrrr
Copy link

JohnFrrr commented Sep 18, 2025

Hi! I need to create a similar provider, and this one is being a great starting point, thank you!
I just had to make 3 changes in the wadm.yml to make it work, without any of them there was either an error in the deployment or an internal error in the app. Not sure if this is the right way to solve it, but it's what worked for me, so just sharing my solution:

  1. Add annotations:
    Before:
metadata:
  name: cron-scheduler-demo

After:

metadata:
  name: cron-scheduler-demo
  annotations:
    version: v0.0.1
    description: "A cron job scheduler demo"
  1. Change "target_config:" to "source.config:":

Before:

target_config:
  - name: cron-config

After:

source:
  config:
    - name: cron-config
  1. Remove the semicolon at the end of the JSON:
    Before:
    cronjobs: job_1=0 * 1 * * ?:{"x1":"foo","x2":"bar"};
    After:
    cronjobs: job_1=0 * 1 * * ?:{"x1":"foo","x2":"bar"}

Copy link
Member

@brooksmtownsend brooksmtownsend left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Well done @Aditya1404Sal !! This looks good to me, the only ask I have is to take a look at @JohnFrrr's feedback and push changes if necessary!

@Aditya1404Sal
Copy link
Author

@JohnFrrr , @brooksmtownsend Thank you so much for trying it out and reviewing it !! I'll definitely get those changes incorporated as soon as I can !!! 😄

…g, Remove the semicolon at the end of the JSON

Signed-off-by: Aditya <aditya.salunkh919@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants