Passing in an argument within a bash script - bash

Question

I have a bash script that I use to call a java class and I pass two arguments to this java class. The first argument ($1) is the string that I pass and it contains someone's name. The second argument ($2) is the previous month as a two digit number (also passed in by the user).
So the java class is called like this:
java -DCONFIG_DIR=... com.example.myapp.grades.gradingProcess $1 $2
However, now, I don't want the user to pass in the second argument and instead, I want the script to determine the month.
Can I do something like this?
month=`date +'%m' -d 'last month'`
java -DCONFIG_DIR=... com.example.myapp.grades.gradingProcess $1 $month
And when I run my script, it'll be something like this: ./myscript.sh 'John'
and not pass in a two-digit month since I'm already doing it inside the script?
Or is that not the correct way to go about it?
Sorry if this seems like an elementary question, I'm still trying to get used to bash scripts.
Thank you?

Answer 1

If you are looking for how to supply a default value in the shell, there is an operator for that.
month=${2-$(date -d 'last month' +%m)}
java -stuff "$1" "$month"
Now, if there was a value in $2, month will be set to that; otherwise, the default will be used. The notation ${variable-value} supplies the value of variable or, if it is unset, the text value. (There is also ${variable:-value} which produces value if variable is set but empty as well.)
(This could be inlined into the java command line, even, though using a variable to break it up is probably better for legibility.
java -stuff "$1" "${2-$(date -d 'last month' +%m)}"
Notice also how you basically always put user-supplied variables in double quotes.)

Answer 2

A few thoughts: time zone, leading zero, and leveraging Java rather than bash.
Time zone
Determining the current month requires a current date. Determining the current date requires a time zone.
For any given moment the date varies around the globe. For example, a few minutes after midnight in Paris is a new day while still “yesterday” in Montréal.
When you do not specify a time zone, a current default time zone is implicitly applied. Be aware that the default can change at any moment. And depending on the default means your code is relying on an externality outside your direct control. And it means results will vary.
So around the ending/beginning of the month you could be getting the wrong month number determining on the time zone in play.
Leading zero can mean octal in Java
The %m you are using produces two digits. Single digit month numbers will have a leading zero. Ex: 09
Be aware that in some situations in Java a number with a leading zero is interpreted as a octal number (base 8) rather than a decimal number (base 10).
Let Java do the work
I suggest it makes more sense to let the Java class do the work of determining the previous month. The bash line should be passing the desired/expected time zone rather than the month, if anything.
ZoneId zoneId = ZoneId.of( "America/Montreal" ) ;
int previousMonthNumber = LocalDate.now( zoneId ).minusMonths( 1 ).getMonthValue() ;
Tip: In Java, even better to use an object from the Month enum rather than a mere integer. Makes your code more self-documenting, type-safe, and guarantees valid values.
Month month = LocalDate.now( zoneId ).minusMonths( 1 ).getMonth() ;